RezetHub · build status

RezetHub — Build Status

Where the proof-layer build stands against its milestones, projected from the live engineering ledger against measured delivery velocity.

Delivered
163
tasks merged behind gates
Effort remaining
~107 eng-days
≈ 644 engineer-hours
v1 build window
9–15 wk
gated · dependency-ordered
Live pilot gate
external
customer-scheduled
Flow · 7d
+29
102 filed / 73 done

Milestone timeline · Aug – Nov 2026

Bars span each milestone's remaining work: dark = parallel (agent fan-out) pace, lighter = steady pace. ◆ gates are fixed acceptance demos and don't compress with velocity.

Stream
AugSepOctNov
M1 · Accounts & onboardingprovisioned B2B sign-in — finishing
finish
Platform · tenancy, deploy & staff toolsorg identity · staff portal · cloud deploy
tenancy · staff portal · deploy
M2 · Provenance engine — hardeningreliability & edge-case pass
reliability hardening
M2 · Unified operations APIone command layer across the app
unified command layer
M3 · Energy & carbon accountingthe main remaining build
energy · emissions · Scope 2/3
M3 · Audit export & monitoringexport · history · data-erasure
audit export · monitoring
M4 · Product Passport & AI assistanttextile passport · operator AI
passport · AI operator assist
◆ Milestone gatesacceptance demos · fixed, don't compress
M2 · end-to-end demo
M3 · audit demo
M4 · live pilot
parallel → steady range gate external (pilot) today

Milestones

Capabilities each milestone delivers, with completion against its scope.

M132/36 · 89%

Identity & onboarding

Provisioned B2B accounts, magic-link login, multi-role organisations.

  • Top-down provisioning: SuperAdmin → Organisation → initial Org Admin → Users
  • Magic-link login (login-only, no self-serve signup), org email-domain allowlist
  • Multi-role organisations (Manufacturer / Recycler / Generator / Buyer / Logistics)
  • Actor-based access model with platform-role overlay
◆ M1 staging acceptance ✓4 open · ~14h
M269/106 · 65%

Provenance engine

The proof layer: event-sourced custody, mass-balance composition, tamper-evident audit.

  • Full custody chain across Generator → Logistics → Recycler → Compliance
  • Many-to-many mass-balance material tracking (kg in vs kg out) with reconciliation
  • Tamper-evident audit trail (cryptographically sealed, independently verifiable)
  • Unified operations API + full MVP feature set on the new architecture
◆ End-to-end chain + tamper-proof demo37 open · ~240h
M35/18 · 28%

Carbon & audit

Operational-carbon measurement and audit-grade export — the main remaining build.

  • Energy & operational-carbon measurement (GHG Scope 2 dual-method + Scope 3 T&D)
  • Audit tools: data export, point-in-time history, GDPR erasure
  • Proof-pack + client impact report generation
  • System monitoring: pipeline health & performance metrics
◆ Audit-verification demo13 open · ~226h
M41/7 · 14%

Digital Product Passport & pilot

Complete textile DPP, AI operator assistant, and a live pilot with a real product.

  • Complete textile Digital Product Passport (EU ESPR delegated-act informed)
  • AI operator assistant wired to provenance commands with approval loop
  • Data-residency alignment for personal / compliance stores
  • Live pilot: real textile product, intake → passport
◆ Live pilot — real textile product · external6 open · ~26h

Reading the projection

Why this is a range, not a date

  • Discovery still outpaces delivery. Building surfaces new hardening + epic-decomposition work; the open count moves with scope, so we track milestone burn-up, not a shrinking counter.
  • Points are re-estimated for epics. A point ≈ one engineer-hour, but epics (energy, dispatch) are sized as the multi-week builds they are, so the hour total doesn't read falsely low.
  • Gates are calendar-bound. The live pilot needs a real product and customer window — agent parallelism compresses code, not the pilot. The right edge stays soft by design.

What "done" means here

Every milestone closes on an acceptance gate — a live demo signed off by an independent verifier, not a self-report. M1's gate is signed off; M2's end-to-end chain demo is next.

Delivery is proven by merged commits behind objective gates (build · tests · security · architecture analyzers · independent verifier). This page regenerates from that same ledger.

Method. Effort = engineer-hours (H≈8 · M≈4 · L≈1.5; epics re-estimated in the fixed milestone spine). Measured delivery throughput over the last 30 days ≈ 29 engineer-hours/day (agent-accelerated) — the build window above is bounded by build dependencies (energy is a serial build) and the external pilot gate, not by raw throughput, so it is deliberately longer than effort ÷ throughput. Milestones are fixed; task data regenerates live from the ledger. Snapshot 2026-08-04, HEAD 7e3451c. Recent merges: magic-link login, seeder hardening, AWS deploy pipeline, textile localisation, dispatch reliability, onboarding surface.