Layer 5 Reporting: Advanced Reporting v1 Live. Live Cockpits Built On GCS.

By Michael Leslie Atkinson · Founder, 905WOOD.COM SALES · May 7, 2026 · 7 min read

---

Advanced Reporting v1 — what it actually replaces

Magento ships with a generic Business Intelligence panel. It is built for storefronts that sell SKUs, not for industrial logistics platforms that route Mothership loads against CIRCIL Levy bands. On May 3 at 905wood.com/advanced-reporting/?v=1, the Advanced Reporting v1 dashboard went live and replaced the generic panel for 905WOOD's purposes. Four sections. Three charts. The data source is the pristine V2 corpus that Pristine Enhancement zero-NULLed on May 1 at 12:44 EDT. The view is the Digital Refinery view — Mothership loads, Compliance Gate verdicts, CIRCIL Levy spread captured, Diversion Pass redeemed. The numbers reconcile with the Quote Pricing Bridge that signed off on May 2. The reporting layer now reads the same source of truth that the cart and the quote and the dispatch dashboard read.

This matters because audit reproducibility runs on consistency between the operator-facing dashboard, the customer-facing invoice, and the auditor-facing report. When all three derive from the same corpus, a regulatory request for "show me the load classified at 14:32 EDT on this date" returns one answer across every screen. The Time Machine is what froze the model and dataset and regulatory text at the millisecond of validation. Advanced Reporting v1 is what surfaces it for review without re-querying the underlying graph.

Live Cockpits v1 — built on GCS, refreshable forever

On May 1, two Live Cockpits shipped. The first was the lead-funnel-cockpit — a self-contained HTML view that reads from the Google Cloud Storage bucket gs://905wood-dr-evidence and presents the inbound Twilio plus Chatbase plus webhook lead state across the prior fourteen days. The second was the delta-marketing-strategy-cockpit, which surfaces the forty net-new marketing plays seeded into gs://905wood-dr-evidence/strategy/delta-marketing-plays-v1.json. Both cockpits are GCS-backed, which means the underlying data updates without redeploying the cockpit. The cockpit is the view. The bucket is the source of truth. The reload button on the cockpit's header refreshes the view against the bucket.

The architectural significance of the GCS-backed cockpit is that any Layer 5 reporting view can be persisted, refreshed, and audited without re-running an analysis from scratch. That is the difference between a chat-rendered table that disappears when the conversation closes and a permanent dashboard that the founder can re-open in a month and see the current state. The pattern was packaged as the gcs-cockpit-builder skill on the same day for reuse across the rest of the reporting set.

The Twilio weekly intelligence pipeline

On May 2, the Twilio Weekly Intel for the prior week pulled 545 inbound calls and 8,540 SMS into the lead-funnel-cockpit. Twenty-three Tier-1 Ontario follow-up candidates were identified across the volume. None have been outbound-contacted because the Twilio Studio autoresponder loop remains a P0 — 8,398 messages went to short codes 22395 and 78156 inside the same week with a 98.3 percent fail rate, and any outbound activity that compounds with the loop risks regulatory complaint volume on 10DLC SMS. The fix is queued. The candidate list is queued behind it. The pipeline itself works — the ingestion is clean, the deduplication is clean, the candidate scoring runs against the V13.0 Sales Knowledge Base. The bottleneck is Studio configuration, not data.

The 9-Point Certificate of Origin — the audit container

The Layer 5 output that travels with every cross-border load is the 9-Point Certificate of Origin. The black-and-white fax-ready PDF format is engineered for CBP officer scrutiny at the Ontario-Michigan crossing. The nine elements have been documented in the V1 blog post on USMCA Shield 812-percent ROI and in the prior post on Layer 3 Regulatory in this V2 series. What changed between May 1 and May 6 is not the certificate itself. What changed is that the inputs to the certificate — the GPS attestation, the Compliance Gate verdict, the AlloyDB regulatory citation, the Vertex ML Metadata pin — now derive from a single source of truth that the Layer 5 dashboard surfaces. The certificate matches what the cockpit shows. The cockpit shows what the dispatch dashboard shows. The dispatch dashboard shows what the Quote Pricing Bridge bills against.

CORC and the Carbon Dividend — what gets minted

Every clean-classified Mothership load yields roughly fourteen-point-three-six tonnes of CO2-equivalent against a verified-feedstock baseline (zero-point-seven-five times nineteen-point-one-five tonnes net weight). At the current CORC market price of approximately three hundred fifty Canadian dollars per tonne, the Carbon Dividend per Mothership clean load lands near five thousand dollars. The 905WOOD ledger retains one hundred percent of the CORC. The customer invoice surfaces it as informational. The audit chain — JSON lineage plus blockchain hash binding the GPS, the model version, the timestamp — proves the saw blade to soil chain that registries require for offset issuance. The CHAR Technologies Thorold facility, the Index Energy Ajax facility, and the Leamington greenhouse offtake confirm the destination side of the chain.

The CORC registry integration is not yet self-service. The Layer 5 Operon Scientific Workspace integration that backstops the registry submission is held for the lab.905wood.com release. The ledger captures it. The cockpit surfaces it. The customer-facing invoice does not currently retain it because the registry retains it. That is the architectural choice — the customer benefits through the lower CIRCIL Levy at Layer 4, the platform retains the CORC at Layer 5.

ForestEdge API — what gets exposed

The ForestEdge API is the Layer 5 output for enterprise customers' Scope 3 climate compliance dashboards. The audited diversion record from a 905WOOD Mothership load returns to the customer's ESG platform as a Scope 3 emissions reduction line item with the cryptographic lineage attached. Procurement directors increasingly require this kind of high-integrity climate data because their own auditors require it. The Digital Product Passport is the JSON-based extension of the same record — saw blade origin, verified diversion, biocarbon yield, end-of-pipe Craft 4.0 biocomposite-brick destination. The 2027 Craft 4.0 framework — the "Return-to-Sender Loop" where refined waste re-manufactures into biocomposite construction material — closes the circular loop and gives the Digital Product Passport its destination.

ForestEdge is not yet public. The data that feeds it is now pristine. The cockpit pattern that exposes the data is now built.

Three things to do in 2026

• Open the Advanced Reporting v1 dashboard at 905wood.com/advanced-reporting/ on a multi-year contract review. The CIRCIL Levy spread captured over the prior twelve months is the single most predictive line for the V9 D219 contract anchor.
• Request a ForestEdge integration brief for your ESG dashboard. The Scope 3 line item is what your auditor is going to ask about in the 2027 reporting cycle. Beginning the integration in 2026 with the API still in private preview is operationally cheap.
• Pull a Live Cockpit for your own account — a customer-facing version of the lead-funnel-cockpit pattern that renders your firm's Compliance Gate verdict distribution, CIRCIL Levy capture, and CORC retention against your own twelve-month load history.

The reframe

Layer 5 is the layer where the platform speaks to the audiences that pay it — the customer's auditor, the customer's procurement director, the customer's ESG dashboard, the customer's regulator. As of May 1, the cockpits are GCS-backed and refreshable. As of May 3, the dashboard reads the pristine corpus. As of May 6, the Twilio pipeline is captured and waiting on Studio. The Time Machine has something to report against.

---