Apply the highest-confidence findings from the Phase 0→42 forensic sweep
after four scrum-master iterations under the adversarial prompt. Each fix
is independently validated by a later scrum iteration scoring the same
file higher under the same bar.
Code changes
────────────
P5-001 — crates/gateway/src/auth.rs + main.rs
api_key_auth was marked #[allow(dead_code)] and never wrapped around
the router, so `[auth] enabled=true` logged a green message and
enforced nothing. Now wired via from_fn_with_state, with constant-time
header compare and /health exempted for LB probes.
P42-001 — crates/truth/src/lib.rs
TruthStore::check() ignored RuleCondition entirely — signature looked
like enforcement, body returned every action unconditionally. Added
evaluate(task_class, ctx) that actually walks FieldEquals / FieldEmpty /
FieldGreater / Always against a serde_json::Value via dot-path lookup.
check() kept for back-compat. Tests 14 → 24 (10 new exercising real
pass/fail semantics). serde_json moved to [dependencies].
P9-001 (partial) — crates/ingestd/src/service.rs
Added Optional<Journal> to IngestState + a journal.record_ingest() call
on /ingest/file success. Gateway wires it with `journal.clone()` before
the /journal nest consumes the original. First-ever internal mutation
journal event verified live (total_events_created 0→1 after probe).
Iter-4 scrum scored these files higher under same prompt:
ingestd/src/service.rs 3 → 6 (P9-001 visible)
truth/src/lib.rs 3 → 4 (P42-001 visible)
gateway/src/auth.rs 3 → 4 (P5-001 visible)
gateway/src/execution_loop 4 → 6 (indirect)
storaged/src/federation 3 → 4 (indirect)
Infrastructure additions
────────────────────────
* tests/real-world/scrum_master_pipeline.ts
- cloud-first ladder: kimi-k2:1t → deepseek-v3.1:671b → mistral-large-3:675b
→ gpt-oss:120b → devstral-2:123b → qwen3.5:397b (deep final thinker)
- LH_SCRUM_FORENSIC env: injects SCRUM_FORENSIC_PROMPT.md as adversarial preamble
- LH_SCRUM_PROPOSAL env: per-iter fix-wave doc override
- Confidence extraction (markdown + JSON), schema v4 KB rows with:
verdict, critical_failures_count, verified_components_count,
missing_components_count, output_format, gradient_tier
- Model trust profile written per file-accept to data/_kb/model_trust.jsonl
- Fire-and-forget POST to observer /event so by_source.scrum appears in /stats
* mcp-server/observer.ts — unchanged in shape, confirmed receiving scrum events
* ui/ — new Visual Control Plane on :3950
- Bun.serve with /data/{services,reviews,metrics,trust,overrides,findings,file,refactor_signals,search,logs/:svc,scrum_log}
- Views: MAP (D3 graph, 5 overlays) / TRACE (per-file iter timeline) /
TRAJECTORY (refactor signals + reverse index search) / METRICS (explainers
with SOURCE + GOOD lines) / KB (card grid with tooltips) / CONSOLE (per-service
journalctl tail, tabs for gateway/sidecar/observer/mcp/ctx7/auditor/langfuse)
- tryFetch always attempts JSON.parse (fix for observer returning JSON without content-type)
- renderNodeContext primitive-vs-object guard (fix for gateway /health string)
* docs/SCRUM_FIX_WAVE.md — iter-specific scope directing the scrum
* docs/SCRUM_FORENSIC_PROMPT.md — adversarial audit prompt (verdict/critical/verified schema)
* docs/SCRUM_LOOP_NOTES.md — iteration observations + fix-next-loop queue
* docs/SYSTEM_EVOLUTION_LAYERS.md — Layers 1-10 roadmap (trust profiling, execution DNA, drift sentinel, etc)
Measurements across iterations
──────────────────────────────
iter 1 (soft prompt, gpt-oss:120b): mean score 5.00/10
iter 3 (forensic, kimi-k2:1t): mean score 3.56/10 (−1.44 — bar raised)
iter 4 (same bar, post fixes): mean score 4.00/10 (+0.44 — fixes landed)
Score movement iter3→iter4: ↑5 ↓1 =12
21/21 first-attempt accept by kimi-k2:1t in iter 4
20/21 emitted forensic JSON (richer signal than markdown)
16 verified_components captured (proof-of-life, new metric)
Permission Gradient distribution: 0 auto · 16 dry_run · 4 sim · 1 block
Observer loop: by_source {scrum: 21, langfuse: 1985, phase24_audit: 1}
v1/usage: 224 requests, 477K tokens, all tracked
Signal classes per file (iter 3 → iter 4):
CONVERGING: 1 (ingestd/service.rs — fix clearly landed)
LOOPING: 4 (catalogd/registry, main, queryd/service, vectord/index_registry)
ORBITING: 1 (truth — novel findings surfacing as surface ones fix)
PLATEAU: 9 (scores flat with high confidence — diminishing returns)
MIXED: 6
Loop thesis status
──────────────────
A file's score rises only when the scrum confirms a real fix landed.
No false positives yet across 3 iterations. Fixes applied to 3 files all
raised their independent scores under the same adversarial prompt. Loop
is measurable, not hand-wavy.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4.0 KiB
Future Expansion — Advanced System Evolution Layers
Adopted 2026-04-24 from J. The system stops optimizing for task completion. It optimizes for provable execution, repeatable outcomes, resilience under drift, failure, and adversarial conditions.
Layer roster + iteration mapping
| # | Layer | Short form | Target iter |
|---|---|---|---|
| 1 | Counterfactual Execution | Generate synthetic failure variants from each success | iter 5 |
| 2 | Model Trust Profiling | Per-(model, task_type) success rate → routing weight | iter 3 |
| 3 | Execution DNA | Compress successful runs into reusable patterns | iter 4 |
| 4 | Drift Sentinel | Re-validate historical tasks on a schedule | iter 5 |
| 5 | Adversarial Injection | Inject poisoned context / malformed outputs / conflicts | iter 6 |
| 6 | Permission Gradient | Confidence → execution tier (≥0.9 full, ≥0.7 dry-run, ≥0.5 sim, <0.5 block) | iter 3 |
| 7 | Multi-Agent Disagreement | Planner/Critic/Validator — disagreement = signal | iter 4 |
| 8 | Temporal Context | Time-aware memory with decay_score + last_validated_at | iter 4 |
| 9 | Execution Cost Intelligence | Tokens, iterations, cloud_calls, latency per task | iter 3 |
| 10 | Human Override as Data | Capture manual fixes as jsonl rows | iter 3 |
Detail (J's original framing preserved)
1. Counterfactual Execution Layer
Simulate alternate failure paths for every successful task. Real Execution → Success → Generate Variations (env, version, inputs) → Simulate Failure Cases → Store Synthetic Failure Signatures. Purpose: pre-train against unseen failures before real exposure.
2. Model Trust Profiling ← iter 3
Per-(model, task_type) performance tracking.
{ "model": "...", "task_type": "...", "success_rate": 0.0, "failure_modes": [], "trust_score": 0.0 }
Usage: route by trust score, adjust validation strictness dynamically, per-model risk budgets.
3. Execution DNA (Trace Compression)
Successful executions → reusable fragments.
{ "dna_id": "hash", "task_signature": "...", "critical_steps": [], "failure_avoidance": [] }
Replaces doc retrieval with pattern retrieval; faster convergence on similar tasks.
4. Drift Sentinel
Select Historical Task → Re-run Current Env → Compare → If Failure → Mark Drifted → Trigger Re-learning. Detect silent decay; maintain long-term reliability.
5. Adversarial Injection Engine
Inject malformed outputs / outdated docs / conflicting instructions / poisoned memory. Verify validation catches, execution blocks unsafe actions, memory rejects corrupted data. Build system immunity.
6. Permission Gradient Execution ← iter 3
Confidence-based control replacing binary:
- confidence ≥ 0.9 → full execution
- confidence ≥ 0.7 → dry-run + diff
- confidence ≥ 0.5 → simulation only
- confidence < 0.5 → block Inputs: validation score, model trust score, memory match confidence. Risk-aware control; reduced catastrophic-failure surface.
7. Multi-Agent Disagreement Engine
Planner / Critic / Validator; disagreement triggers more context, bigger model, stricter validation. Disagreement is signal, not noise.
8. Temporal Context Layer
{ "created_at": "ts", "last_validated_at": "ts", "decay_score": 0.0 }
Retrieval priority: recent + validated + high success rate. Avoid stale knowledge.
9. Execution Cost Intelligence ← iter 3
{ "task": "...", "tokens_used": 0, "iterations": 0, "cloud_calls": 0, "latency_ms": 0 }
Optimize local vs cloud; reduce unnecessary iterations.
10. Human Override as Data ← iter 3
{ "human_fix": "...", "reason": "...", "task_signature": "...", "validated": true }
Manual fixes become reusable knowledge.
Final Principle
Memory is not passive recall. It is operational substrate:
- failures become structured knowledge
- successes become reusable execution patterns
- all outputs are validated before reuse
System Directive
Not speed. Not convenience. Correctness. Verifiability. Resilience under change.