Build status.
A programmatic, daily-audited view of where Writ is in development.
Every box below represents a Jira story in the WBE project.
Colors are computed from live Jira status + recent commits in
Writ_BE_DEV + filesystem evidence.
No AI interpretation.
- Audited
- Jun 5, 2026, 06:08 AM CDT
- Jira source
- live
- Stories
- 394 across 31 epics
- Rollup
- 80% · 7% · 13%
The long-lived services and architectural capabilities that make up the Writ platform.
Platform Components
Custom Build — 12 Services
AI Paradigm Expansion
The phased build plan, from lab foundation through IL5-scale rollout.
MVP 2-Week Plan
Phase 1 — Foundation
Phase 2 — AI MVP
Phase 3 — Governance
Phase 4 — Assessment
Phase 5 — Scale
Deployment profiles and day-2 operational runbooks.
Deployment Profiles
Day-2 Operations
ATO, CMMC, SSDF, and SBOM/signing infrastructure.
Compliance & Controls
Developer experience, SDKs, reference apps, and market positioning.
Frontend DX
Differentiation
Tracked risks and the mitigations owned by the program.
Risks & Mitigations
Epics created in Jira since the components.json group map was last updated. Move these into a curated group when ready.
Platform robustness + self-healing — stop firefighting classes of errors
Greenfield 2026 architecture-comparison: gap closure
System Verification Harness (L0–L6) — what has actually landed
Admin-UI roadmap: foundation patterns (panel registry, approval UI, log drawer, palette, banner invariant)
Admin-UI roadmap: light up Phase 3 mutations + Phase 4 compliance-ops backends
Admin-UI roadmap: approvals UI + audit-chain browser (close dual-control loop)
Admin-UI roadmap: AI fleet observability — trust/identity/gateway tier (6 services)
Admin-UI roadmap: AI fleet observability — paradigms (data, inference, training, privacy)
Admin-UI roadmap: tenancy, missions, identity admin (Keycloak / SPIRE / cert-manager)
Admin-UI roadmap: supply chain + policy authoring + runtime security
Admin-UI roadmap: AO posture, ConMon, search, notifications, UX polish
External critique 2026-05-03 follow-up: weaknesses & gaps
External OpenAI-client connectivity
infra-identity silent-drift remediation — 18-day Flux failure cascade
35 blocks relationships across 41 tickets.
Only blocks / is blocked by links are drawn here. Softer
relates to links (66 edges) are hidden to keep the tree legible —
hover a story chip above to see its full link list.
Non-green stories with outgoing blocks edges. These are the items actively holding up dependent work.
- WBE-416 blocks 1 Decide license bar: strict MIT/Apache vs. OSS-no-BSL/SSPL/ELv2
This page is regenerated daily by a systemd user timer (writ-status-audit.timer)
that runs scripts/audit-status/index.mjs. The script queries the Jira REST API
for WBE-project issue status, walks the last 60 days of git history in
~/Writ_BE_DEV, and checks for the presence of evidence files. The output is
written to public/build-status.json. The Astro build picks that file up and
renders this page. No AI interpretation is in the loop.
Classification rules — green: Jira status-category = Done · yellow: Jira = In Progress, or any commit mentioning the key in last 60 days · red: no Jira activity, no recent commits.
Dependency-data hygiene. 357 of 394 tracked stories have no blocks / is blocked by links recorded in Jira.
The dependency graph and badges above reflect only what's explicitly linked — implied dependencies (e.g. phase ordering) are not drawn.