CONTEXTCONTROL PRODUCT EXECUTION DIRECTIVE¶

BUILD THE FLAGSHIP UI. USE THE FACTORY. SHOW REAL SHIT.¶

ContextControl.ai is Bluefly's flagship product UI for BluCity.

It is not a documentation exercise. It is not an API catalog demo. It is not a pile of backend entities. It is not a second Gas City.

The immediate product problem is simple:

CONTEXTCONTROL_HAS_NO_COMPELLING_FRONTEND=TRUE CUSTOMER_DEMO_VALUE=LOW PRODUCT_VISIBILITY=POOR

Your job is to make ContextControl visibly useful and product-quality while preserving the architecture.

1. USE THE FACTORY FIRST¶

Before touching Drupal:

gc mail check

Search existing Beads by EFFECT, not by proposed title.

Search at minimum for: contextcontrol, frontend, dashboard, operator, receipt, evidence, mail, agent, activity, approval, api catalog, Convoy G, G6, G10, G11

Then record: EXISTING_BEAD=bc-jv2o CLAIM= OWNER=DRUPAL DEPENDENCIES= CURRENT_PROOF_STAGE= ACCEPTANCE= EVIDENCE_PATH=

Do not ask Thomas which Bead to do next if the dependency graph answers it.

2. FIRST OBJECTIVE: A SHOWABLE CONTEXTCONTROL¶

We need a real product surface immediately. The first frontend slice should make ContextControl understandable within 10 seconds.

Build an authenticated operator dashboard with this product navigation: Home, Work, Agents, Mail, Activity, Approvals, Receipts, APIs, Settings

Use product terminology, not raw Gas City jargon by default: Objective = Mountain, Initiative = Convoy, Work Item = Bead, Workspace = Rig, Procedure = Formula, Automation = Order, Signal = Event, Capability Pack = Pack, Run = Session, Receipt = Operational Receipt.

3. HOME DASHBOARD¶

The first screen should answer: WHAT IS HAPPENING? WHAT NEEDS MY ATTENTION? WHAT IS RUNNING? WHAT FAILED? WHAT WAS VERIFIED? WHAT CAN I DO?

Build a real dashboard using Drupal-native composition. Target layout:

TOP: ContextControl (Governed AI Operations) PRIMARY QUESTION: What needs my attention right now? FIRST ROW: [Needs Attention] [Running] [Blocked] [Verified] SECOND: Current Objectives (objective, initiative, owner, progress, blocker) THIRD: Active Work (work item, agent, current step, age, status) FOURTH: Agents (current run, current work, provider/model, health) FIFTH: Activity (event timeline) SIXTH: Approvals + Mail SEVENTH: Recent Receipts / Evidence

No fake metrics. Show polished empty states (e.g. "WAITING FOR SOURCE", "NOT CONNECTED") if data is unavailable.

4. MAKE IT LOOK LIKE A PRODUCT & USE EXISTING VIEWS¶

Audit existing Views in config/sync (contextcontrol_overview, contextcontrol_dashboard_activity, etc). Do not create new Views if existing ones can be reused.

Use Canvas, SDC, Views, Layout Builder, design tokens, existing theme before custom frontend code. Build reusable components with semantic props (attention-summary, objective-card, receipt-card). Do not write page-specific CSS soup or giant Twig templates.

5. PRODUCT DESIGN REQUIREMENTS¶

ContextControl = operational + dense + calm + evidence-oriented. It should feel: calm, operational, technical, trustworthy, high signal, human-readable. It should NOT feel: Drupal admin, Grafana clone, generic SaaS, AI-gradient dashboard, developer console.

We need a visual language for GOOD, WARNING, BLOCKED, FAILED, RUNNING, WAITING, VERIFIED, HUMAN ACTION REQUIRED using tokens/variants.

6. REAL DATA ONLY¶

Preferred read path: Gas City OpenAPI → api_normalization → normalized Drupal entities → Views / Canvas → operator UI. Events: Gas City Event stream → Drupal integration → ECA → read-model update → UI.

Do not build custom GC REST clients, custom schedulers, custom polling, or copy Dolt directly into Drupal.

7. THE FIRST PROOF IS DELIBERATELY TINY¶

Prove exactly: ONE Objective, ONE Initiative, ONE Work Item, ONE Agent, ONE live status, ONE Event timeline, ONE Receipt. If these seven render correctly and look like a real product, the Bead has a valid frontend proof.

8. VISUAL VERIFICATION & HANDOFF¶

Before Witness: DESKTOP_SCREENSHOT= MOBILE_SCREENSHOT= NAVIGATION_PASS= VISUAL_HIERARCHY_PASS= EMPTY_STATES_PASS= REAL_DATA_PASS= NO_FAKE_DATA=YES NO_CUSTOM_SCHEDULER=YES NO_SECOND_WORK_GRAPH=YES NO_PAGE_SPECIFIC_CSS_HACKS=YES

When implementation is ready: update bc-jv2o → record screenshots/evidence → GC Mail WITNESS → GC Mail BLU → wait on verification → stop.