DasLab v3.0.0 "MUSTAQIL"

DasLab v3.0 "MUSTAQIL" — the org-engine gains its interop and self-host reach: DasLab can call the ecosystem (WS-A), run headless (WS-B), execute on a governed loop substrate (WS-C), observe itself (WS-D), harden its tenant (WS-E), prove a project 0→100 (WS-G), and expose a self-hosted control plane (WS-H) — plus the A2A OUTBOUND surface (WS-I) making DasLab a callable governed agent for another agent system. Every workstream closes its six AADL gates; the tempo go-live (WS-F) reaches GATE-4 and rests at its Founder gate.

Honest scope — everything autonomy-bearing ships OFF

Same discipline as v2.0: a2a_outbound, heartbeat_enabled, and every MUSTAQIL ws_* flag ship default-OFF. With the flags off, dispatch/board behavior is byte-identical to pre-merge (SC-005). No endpoint is published and no autonomous tick runs until a QONUN-5 Founder-only flip. HEARTBEAT go-live remains evidence-gated on a ≥3-day clean shadow window of counted waves (check_heartbeat_readiness.py → NOT READY at 0/3; heartbeat_go_no_go.py → NO-GO). The FR-004 monthly credit ceiling is declared and enforceable (Founder-set active_plan: max_20x, $200/mo).

Added

• A2A OUTBOUND (WS-I) — governed callable-agent surface (ADR-0040): external systems submit a goal proposal (board intake), never a gate approval; publishing is a Founder act; in-tenant only (TN-1); reuses the ADR-0009 admission + ADR-0012 redaction edge.
• ADR-0042 — records the monthly credit ceiling as an outer SI-5 cap (idle + alert), window defined so it cannot latch.
• WS-F go/no-go readiness artifact (three-state PASS/FAIL/UNKNOWN); the SI-5 sanctioned-pause alert limb; per-workstream maintenance health checks.

Fixed (budget/evidence rails — found by adversarial review)

• Monthly credit ceiling compared a lifetime total vs a monthly cap (permanent idle latch) → month-to-date windowed, non-latching.
• Per-day rail enforced the $500 informational org cap instead of the $15 SI-5 ceiling → reads the authoritative mustaqil.caps.
• Go/no-go credit gate could return GO on a corrupted budget config → composes the owning checker.
• Gate-approval scanner read agent-signed gates as human → human-actor allow-list, fail-closed.
• created_at write seam admitted non-canonical timestamps that vanished from budgets/evidence → rejected at the seam with a visible drop count.

diagnostics 100/100 · full suite 2614 passed / 25 skipped · board_lint 0 violations · gitleaks clean.

DasLab v2.0.0 — ORGANISM

DasLab v2.0 "ORGANISM" — a governance-first, file-native AI software organization of 32 Claude Code subagents gains a durable, observable, self-evaluating substrate. A fresh git clone boots the entire org.

Highlights

• Durable runs — every wave gets a run-id, wave checkpoints, and a committed doubly hash-chained attestation. Crash-safe resume/fork with zero lost or duplicated tickets (kill-drill verified).
• Observability & cost — OTel-shaped span events per dispatch, a per-run cost ledger, and committed, git-auditable KPI evidence. The T1–T7 gates read from real spans, not vibes.
• HEARTBEAT autonomous tempo — a scheduler substrate with ADR-0027 safety rails. It ships OFF / shadow by design; going live is a Founder-only, evidence-gated act (scripts/check_heartbeat_readiness.py, docs/runbooks/heartbeat-go-live.md).
• Golden-eval competence — all 32 roles carry ≥3 deterministic golden tasks scored ≥0.80 at their assigned tier, guarded by an anti-gaming probe: empty-submission detection plus a strict task.md answer-leak detector (a prompt example that scores through its own verifier fails CI).
• Project-OS gateway — a documentation pack compiles into a project board of self-contained story tickets the org delivers 0→100 through the six AADL gates.
• Governance & integrity — the QONUN laws, AADL six-gate lifecycle, and anti-gaming metrics remain load-bearing; diagnostics.py is a 100/100 all-or-nothing gate, and CI has real teeth (no continue-on-error escapes).

Honest scope of "2.0"

The autonomous-tempo loop ships shadow / off by design. The §5 live-tempo KPI rows — T1 busy_fraction, T3 concurrency, T4 model-mix — are measured from real operation and therefore accumulate once the loop goes live (a ≥3-day counted-wave window, then flipping heartbeat_enabled: true, evidence-gated by check_heartbeat_readiness.py). No KPI number in this release is fabricated — unmeasured is reported as unmeasured. See CHANGELOG.md and docs/runbooks/heartbeat-go-live.md.

Quality gate at release

diagnostics.py 100/100 · full test suite green (1757 passed) · agent_eval --all --enforce 32/32 · anti-gaming, import-ban, and comm-flows gates all green · gitleaks clean.

Released as a clean-slate snapshot (no donor history). License: Apache-2.0.

DasLab v1.0.0

DasLab v1.0.0 — the first public release of a reproducible operating system for a 32-agent AI software organization. A fresh git clone boots the entire org.

Highlights

• 32-agent organization — a four-level hierarchy across six departments, generated from the org tree + the model-allocation policy (opus ×10 / sonnet ×19 / haiku ×3).
• File-based board + the /daslab-plan, /daslab-cycle, and /daslab-run orchestration skills — no timer, no server, no API.
• AADL — six gated lifecycle stages (Planning → Design → Development → Testing → Deployment → Maintenance).
• 100/100 release gate (scripts/diagnostics.py) + a CI-enforced validator suite, including a fail-closed lint gate.
• DGO-X — a graph-orchestrated, gate-driven control plane in shadow mode.
• ArcRift — an optional persistent-memory loop (recall-at-start / store-at-end, scoped per project).
• Full documentation: README, docs/ARCHITECTURE.md (with diagrams), docs/USAGE.md, the ADR set, and CONTRIBUTING / SECURITY / CODE_OF_CONDUCT.

See CHANGELOG.md for the full entry. Licensed under Apache-2.0.