Change Digest — 180 Days

Scope: A narrative of what the platform became between mid-May and early November 2026 — capability by capability, quarter by quarter — read from the commit stream (2,005 commits counted over the window; the stream markers total 2,174 across two rollups, so counts differ by rollup but agree in magnitude). Audience: operator + developer. Status: computed 2026-11-09 from commit subjects, author aggregates, and directory-touch aggregates; no code bodies were read beyond the cited subjects. Sources (cited inline): the commit stream itself and its author/month aggregations. Aggregations are bounded streams (git log piped to grouping commands); no per-commit loops were used for counts.

The arc in one paragraph

The window opens with the Sovereign and Truth-Graph foundations in May (BFF, staging, commerce, end-to-end smokes, and truth-graph checkpoints CP0–CP10) alongside the universal-identity cryptographic waves. It pivots in June to the zero-trust claim-operations platform — claims, proof of correct execution, and quorum become the spine — then hardens through the summer into governance, the vertical registry, the jobs platform, and the protocol-hand gateway. July to September stands up the notification and construction verticals, the mesh, and the workflow engine, and wires the agriculture integration. October is the declarative and convergence wave: the truth-graph declarative track, the proof-of-execution bridge into the protocol gateway, sourcing ticks, unified verticals. November is the commercialization sprint — claims and financial-monitoring backlogs completed, a weekly review that refines the backlog, and a lifecycle event-spine consumer — capped by this platform map itself. One lineage note the reader may see in older digests is deliberately not narrated here: an external database migration and removal ran in the autumn subjects; the surviving platform is a single database plus the messaging fabric everywhere.

Who did the work

Two authors carry the window, with a small automation tail (source: author aggregation over the 180 days).

The theme mix over the same subjects is feature-dominant with a heavy fix tail: roughly 958 feature subjects against 508 fix subjects, with the runtime BFF the brightest subsystem (~179 subjects), agriculture the top vertical (~128), construction second (~124), messaging (~107), integration (~70), the protocol gateway steady from June to November (~60), governance (~52), claims (~46), and the jobs platform (~34). The largest single-token narrative in the subjects is the wave family across the mesh, the identity waves, and the truth-graph declarative track. These are salience signals, counted as raw subject hits; overlapping keywords double-count, so read them as emphasis, not as a partition.

Q2 2026 — foundations and the claim pivot (May–June)

May (103 commits). The month that proves the platform can run. The repository sync and DevOps alignment baseline lands first; within a day the truth-graph platform completes CP0–CP10 with outbox retry and BFF guards, the sovereign agent app and planning strata ship with a dev bootstrap, and the dev gateway stands up. Commerce follows: the billing stack with triple-write subscriptions and consolidated smokes, corrected for the data-store version. The foundational knowledge primitive gets its root attributes with index-backed queries. In parallel, the cryptographic identity stack opens — a crypto-first universal identity claim implementation and the first identity waves (revocation cascade, threshold co-signing, federation, ledger anchoring, audience-bound presentations).

June (381 commits). The pivot. The zero-trust claim-operations platform becomes the organizing idea; quorum, proof of correct execution, community governance, the vertical registry, the jobs platform, and the protocol gateway all acquire the subjects that will carry them for five months. The BFF decomposes into the runtime tier; the agents' workflow engine and the flow/pool/fsm surfaces set the division of labour the rest of the window refines.

Q3 2026 — verticals and hardening (July–September: 388 + 214 + 458)

July (388 commits). The declarative-first directive is persisted, with the first claim-transition functions (offer ingestion, requirement binding, incident resolution) that later months will document as routes. The notification platform, construction vertical, mesh, and workflow engine take shape as vertical platforms rather than demos.

August (214 commits). The quieter month carries integration weight: agriculture and fleet logistics wiring, the mesh expanse, and the compliance gate family that October will complete.

September (458 commits). The busiest month of the window. Vertical depth arrives — agriculture's universal task fabric and onboarding phases, construction's unified platform and desk series, the jobs saga with its sourcing attestation and labour-mobility protocol route. The protocol gateway's authenticated connectivity, correlation processors, and declarative routes all land here, and the governance and quorum desks harden. Subjects this month read as production-hardening rather than greenfield.

Q4 2026 — convergence, then commercialization (October–November: 352 + 109)

October (352 commits). Convergence. The truth-graph declarative track ships its first waves; proof-of-execution session lifecycle is encapsulated inside the protocol gateway, eliminating direct database queries from the flow; sourcing ticks and unified verticals standardize the verticals onto the same fabric. The theme that unifies the month is declarative: behaviour declared in configuration and pushed down to the endpoints, not hardcoded.

Early November (109 commits). The commercialization sprint, and the window's closing argument. Route documentation follows the declarative directive (standing-order playbooks declared, not tabled). The identity and ontology work aligns the event catalog. The program suite (brand boundaries, the system-of-record declaration, the product map, the zero-trust PII posture, the agency charter with its freeze list and CI check, and the agency emergency protocols) lands in a tight cluster on 7 November. The claims and financial-monitoring backlog completes on 8 November with guarded transitions, SLA/quorum/value-added-service desks, the compliance gate family, and dual-control operations; the fleet bridge goes live the same day. The weekly review refines the backlog into a numbered review queue; the lifecycle event-spine consumer closes the window on 9 November alongside this map.

Theme clusters (context for the narrative, not a separate story)

• Protocol gateway. Authenticated connectivity with end-to-end tests passing, correlation and error processors, declarative routes — the hands of the platform, carrying the agency, emergency, and jobs protocols.
• Quorum. Ballot closure, hard desks, scratch-and-gather, signing — the trust mechanism behind the claims bands.
• Proof of correct execution. Encapsulation into the gateway, mission-critical soft desks, the journal, and the storage bridge — the audit spine every governed flow cites.
• Verticals. Agriculture's task fabric and phased onboarding; construction's unified platform and desk series; the jobs saga; transport's fleet bridge — each a platform, none a demo.
• Claims. The builder spine, the validation registry, enforcement, and the safe-emission fix that keeps identifier strings honest.
• BFF. Decomposition, route recovery, and a steady production-hardening rhythm.
• Waves. The mesh waves, the identity waves 10–30, the truth-graph declarative waves 0–4, and the agriculture universal-operations waves — the program's recurring unit of delivery.

Month-by-month landmarks (how each month reads)

These are not a count table; they are the capability moments an operator would have noticed, in order. Hashes and subjects are from the same stream the counts above were read from.

May 2026 — the platform proves it can run.

• Repository sync and DevOps alignment is the baseline; truth-graph checkpoints complete with outbox retry and guard composition the next day.
• The sovereign agent app and planning strata arrive with a dev bootstrap; a dev gateway follows for third-party API paths.
• Commerce ships its billing stack with triple-write subscriptions and consolidated end-to-end smokes, corrected for the 3.0.5-era database behaviors.
• The knowledge primitive gains root attributes with index-backed queries; cryptographic identity opens with the first waves — revocation, threshold co-signing, federation, ledger anchoring, audience-bound presentations.
• An FSM view engine with encrypted-payload state and caching, plus registration and traffic-scenario enrichment, closes the month.

June 2026 — claims become the spine.

• The zero-trust claim-operations pivot precedes the densest part of this month's stream: quorum, proof of correct execution, community governance, the vertical registry, and the jobs platform all acquire sustained subjects.
• Internal build rhythm peaks on two days at month start and mid-month, with the BFF decomposition and agent-fabric work visible throughout.

July 2026 — declaration over implementation.

• The declarative-first directive is persisted with the first claim-transition functions — every later quarter extends this idea.
• Notification, construction, mesh, and workflow-engine surfaces harden from demos toward platforms.

August 2026 — integration weight.

• Agriculture and fleet-logistics wiring and the compliance gate family carry a quieter commit count with production consequence.
• Subjects read as integration and hardening rather than new surfaces.

September 2026 — the busiest month.

• Agriculture universal task fabric, multi-mode hierarchy, phased onboarding, and the fabric-scrub series ship in waves.
• Construction's unified platform, domain backend, and desk series ship alongside; the jobs saga gains its attestation workflow and mobility protocol route.
• The protocol gateway gains authenticated connectivity, the full end-to-end test set passing, correlation processors, and declarative routes; governance and quorum desks harden in parallel.

October 2026 — convergence on the declarative fabric.

• The truth-graph declarative track ships its first waves.
• Proof-of-execution session lifecycle moves inside the protocol gateway, removing direct database queries from that flow.
• Sourcing ticks, unified verticals, and fleet, billing, and commerce-service integrations standardize the verticals onto one fabric.

November 2026 — commercialization closes the window.

• Idle-mandate and governance-hardening subjects persist through 7 November: fleet compose soft stubs, fleet bridge runtime verification, and the integrator verifier proving the gateway's contract surface is reachable.
• The program suite lands in one cluster: brand boundaries, the system-of-record declaration, the product map, identity design, the agency freeze charter, emergency protocols.
• Claims and financial-monitoring backlogs complete — guarded transitions, SLA, quorum, and value-added-service desks, the compliance gate family, dual-control operations — followed by the weekly review and its numbered review queue.
• The lifecycle event-spine consumer and this platform map close the window.

Where to go next

• Program narrative: the platform-program document and the commercialization backlogs (claims, entities, sourcing, requests) carry the epic-level story; the truth-graph master index carries strata and test detail.
• Contracts: the spec index in this directory for how a route becomes a published API; the BFF catalog for the tier-by-tier interface map; the workflow guide for the day-to-day loop.

Reproducibility (verbatim commands)

git log --since='180 days ago' --pretty=format:'%an' | Group-Object | Sort-Object Count -Descending
git log --since='180 days ago' --pretty=format:'%s' > $env:TEMP\s.txt
@('feat','fix','materra','kujenga','kazi','usafiri','bff','nats','camel','claims','poce','quorum','governance','kutuma','kestra','commerce','vault','truth-graph','integration') | ForEach-Object { $c=(Get-Content $env:TEMP\s.txt | Select-String -Pattern $_ | Measure-Object).Count; "$_ $c" }
git log --since='180 days ago' --name-only --pretty=format:'SUBJECT-BREAK' | Select-String "SUBJECT" | Measure-Object | Select-Object Count
git log --since='180 days ago' --pretty=format:'%ad %h %s' --date=short | Select-Object -First 60
git log --since='180 days ago' --pretty=format:'%ad %h %s' --date=short | Select-Object -Last 70

All counts above come from those streams; the surviving-platform note in the arc reflects the same window's subjects.