Commissioning Dashboard

The factory floor control panel. One view of every capability: what's specified, what's built, what's proven.

In factory engineering, the team that builds a system is never the team that commissions it. The builder knows what they intended. The commissioner checks what actually shipped.

Capability Status Matrix​

Every Mycelium capability, scored on a 5-level maturity scale:

Active Capabilities​

Table order = build order. Matches Active table.

Backlog Capabilities​

Platform Capabilities​

Aggregate Health​

The system has depth in two capabilities (CRM/RFP and ETL) and breadth in specifications. Nothing has reached L3 (tested) or L4 (commissioned) yet.

Flight Readiness Gates​

Before any capability ships to production, it must pass eight gates. Adapted from factory pre-flight inspection.

Four Golden Signals (G6)​

Current Gate Status (Sales CRM — only app in production)​

No other capability has reached the gate stage yet.

Revenue Readiness​

Capabilities ordered by proximity to generating revenue.

RFP: The Wedge​

The closest capability to revenue. Key metrics:

Speed is a feature. Accuracy is the product. Win rate is the proof.

Kill Criteria (90 Days: 2026-03-24)​

Infrastructure Backlog​

Shared infrastructure that multiple capabilities depend on.

Commissioning Process​

How a capability moves from L0 to L4:

L0: SPEC ONLY           L1: SCHEMA + API        L2: UI CONNECTED
PRD written        →    Backend exists      →    Users can interact
Features defined        Schema deployed          CRUD works
Success criteria        API endpoints live       Workflows complete
Kill signal set         Integration tests        Manual QA passes

L3: TESTED              L4: COMMISSIONED
Automated tests    →    Independent verification
E2E suite passes        Commissioner reads spec
Performance gates       Commissioner opens browser
Regression suite        Commissioner checks features
                        Pass / Fail + evidence

Commissioning Protocol​

1. Commissioner reads the PRD (not the code)
2. Commissioner opens the live application
3. For each row in the Feature / Function / Outcome table:
   • Can the feature be found?
   • Does the function work as specified?
   • Does the outcome match the success criteria?
4. Record Pass / Fail with evidence (screenshot, recording, measurement)
5. Update the PRD commissioning table
6. If all critical features Pass: capability is L4 Commissioned

The commissioner is never the builder. The builder knows what they intended. The commissioner checks what actually shipped.

Prioritization Algorithm​

Full scoring methodology, current PRD scores, hierarchy map, and duplication audit: Work Prioritisation.

Use one standard scoring process for every PRD in this factory.

This follows the Tight Five sequence for business execution:

1. Principles: is value transformation and distribution explicit?
2. Performance: are benchmarks and drift triggers defined?
3. Platform: can we ship on existing operational base?
4. Protocols: does this create reusable know-how?
5. Players: is demand real and are the right people onboard?

Scorecard (0-5 each)​

Weighted Priority Score​

Use this weighted formula:

PRIORITY_SCORE =
  (0.20 * Principles) +
  (0.25 * Performance) +
  (0.20 * Platform) +
  (0.15 * Protocols) +
  (0.20 * Players)

Why this weighting:

• Performance is highest weight because unmeasured work drifts.
• Principles/Platform/Players are equal core constraints.
• Protocols still matter, but after value, measurement, and demand are clear.

Hard Gates (No Gate, No Build)​

If any gate fails, priority is HOLD regardless of score.

Decision Bands​

Drift Control (Factory Cadence)​

Run this every week for active PRDs:

1. Recompute Priority Score
2. Evaluate benchmark state: Pass / Warn / Fail
3. Trigger action:
   • Pass -> continue or promote standard
   • Warn -> corrective loop and retest in 7 days
   • Fail -> freeze rollout, rollback, or kill
4. Log the decision and evidence in this dashboard

This keeps prioritization aligned with construction/manufacturing discipline: standard fittings, measurable tolerances, and independent inspection.

Next Actions​

Ordered by ROI — highest leverage moves first. Kill date: 2026-03-24 (28 days).

Tier 0: Prove Outbound + Unblock Agent Profiles (3.5 days engineering)​

Tier 1: Wire for Revenue (~6 days engineering)​

Tier 1.5: Build Sales Dev Agent (~14 days engineering, parallel with Tier 1)​

Tier 2: Wire for Agent Amplifier Position (~11 days engineering)​

Tier 3: Close the Loop​

Context​

• Phygital Mycelium — The capability catalogue
• Mushroom Caps — The ventures that compose from these capabilities
• JTBD Superset — The demand map
• Benchmark Standards — Trigger-based benchmark protocol
• Wallet Safety Benchmarks — Wallet-specific commissioning standard
• Standards — Where proven patterns graduate to
• Flow Engineering — Maps that produce code artifacts