Review

Look under the hood.

Methodology, Hive substrate, ADR-derived decisions, derived state authority. How the work happens — same care visible everywhere.

InternalBuild-verification substrate (internal vocabulary). The narrative account of what's built lives in theKnowledge base and thehandoff corpus.

Hive substrate

104 open · 690 closed. Proposal lifecycle derived from GitHub state per ADR-0055. The live presence + activity dashboard:

Behind a shared preview password (ask the operator) — same gate as the other live demo links.

→ Hive dashboard ↗

Decision record

repo · team access

93 ADRs (Architecture Decision Records), indexed by Hive synthesis ID. Most recent:

  • ADR-0093B2B admin enrollments seed their first charge; PO/net-terms renewals use a separate obligation ledger
  • ADR-0092D1 migration lag is made visible; releases stay operator-gated
  • ADR-0091TypeScript is the backend language for the marketplace substrate — reaffirmed against Rust/Kotlin on a from-scratch basis

Methodology

repo · team access

Dual-track agile, the five-actor model, two substrates. The long-term canon.

METHODOLOGY.md (9 sections)

Ways of working

repo · team access

Right-now operational layer — proposal taxonomy, cadence, spec-change rule. Time-boxed: sunsets when METHODOLOGY §4a is built.

WAYS-OF-WORKING.md

Trust axioms

Three principles for how artifacts behave under multi-agent pressure (i.e. when several AI agents and humans edit the same project concurrently). Ratified 2026-05-13 via Hive synthesis #574. Full text in METHODOLOGY §8 (repo · team access).

  1. 8.1State derives from code, not from docs. The authoritative answer to "what is our current state?" is always the codebase, never any document.
  2. 8.2Canonical-vs-derived ontology. Every doc is either source-of-truth (canonical) or commentary that decays (derived). Frontmatter contract enforces the distinction.
  3. 8.3Audit docs decay fast — snapshots, never authority. Claims about current state must reference a derivation ID, not prose. Re-derive before propagating any prior audit.

Live substrate state

Real-time presence, activity stream, and reaction interactions against the Hive MCP backend (the project's internal proposal/task tracker) live separately — it's an interactive app, not a static derived view. Portal already covers the snapshot data (see GA readiness, Roadmap); the dashboard adds the live + interactive bits.

Open hive dashboard ↗