matrix-agent-validated/truth/staffing.fill.toml
profit ac01fffd9a checkpoint: matrix-agent-validated (2026-04-25)
Architectural snapshot of the lakehouse codebase at the point where the
full matrix-driven agent loop with Mem0 versioning + deletion was
validated end-to-end.

WHAT THIS REPO IS
A clean single-commit snapshot of the lakehouse code. Heavy test data
(.parquet datasets, vector indexes) excluded — see REPLICATION.md for
regen path. Full lakehouse history at git.agentview.dev/profit/lakehouse.

WHAT WAS PROVEN
- Vector retrieval across multi-corpora matrix (chicago_permits + entity
  briefs + sec_tickers + distilled procedural + llm_team runs)
- Observer hand-review (cloud + heuristic fallback) gating each candidate
- Local-model agent loop (qwen3.5:latest) with tool use + scratchpad
- Playbook seal on success → next-iter retrieval surfaces it as preamble
- Mem0 versioning + deletion in pathway_memory:
    * UPSERT: ADD on new workflow, UPDATE bumps replay_count on identical
    * REVISE: chains versions, parent.superseded_at + superseded_by stamped
    * RETIRE: marks specific trace retired with reason, excluded from retrieval
    * HISTORY: walks chain root→tip, cycle-safe

KEY DIRECTORIES
- crates/vectord/src/pathway_memory.rs — Mem0 ops live here
- crates/vectord/src/playbook_memory.rs — original Mem0 reference
- tests/agent_test/ — local-model agent harness + PRD + session archives
- scripts/dump_raw_corpus.sh — MinIO bucket dump (raw test corpus)
- scripts/vectorize_raw_corpus.ts — corpus → vector indexes
- scripts/analyze_chicago_contracts.ts — real inference pipeline
- scripts/seal_agent_playbook.ts — Mem0 upsert from agent traces

Replication: see REPLICATION.md for Debian 13 clean install + cloud-only
adaptation (no local Ollama).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-25 19:43:27 -05:00

33 lines
1.2 KiB
TOML

# Phase 42 — staffing.fill task class rules (file-backed).
#
# These rules mirror what crates/truth/src/staffing.rs registers in code
# via staffing_rules(). Both sets load at gateway startup; rule IDs MUST
# be unique across the combined set, so operator-file overrides require
# changing the in-code registration (or vice versa).
#
# Edit a threshold / add a needle / change a description? File-level
# edits land without a code deploy. Schema changes (new RuleCondition
# variants) still need a code bump.
[[rule]]
id = "fill.endorsed-count-matches-target"
task_class = "staffing.fill"
description = "endorsed_names.length must equal target_count"
action = { type = "Reject", message = "endorsed count does not match target_count" }
[rule.condition]
type = "FieldEmpty"
field = "contract.target_count"
# When target_count is absent entirely, the rule fires and we reject.
# Callers must include target_count; this is the first gate.
[[rule]]
id = "fill.city-required"
task_class = "staffing.fill"
description = "contract.target_city must be present and non-empty"
action = { type = "Reject", message = "target_city is required" }
[rule.condition]
type = "FieldEmpty"
field = "contract.target_city"