Compare commits

..
Author SHA1 Message Date
ed d61fd5b8e0 Merge branch 'tier2/send_result_to_send_20260616' of C:\projects\manual_slop_tier2 into review/send_result_to_send_20260616 2026-06-17 02:15:11 -04:00
ed d17a6004c7 Merge branch 'master' into review/send_result_to_send_20260616 2026-06-17 02:15:04 -04:00
ed 93ccf1b182 chore(tier2): move throw-away scripts to artifacts/ subdir
Tier 2 wrote 23 working scripts to scripts/tier2/ during the
send_result_to_send_20260616 track. These were scaffolding for the
rename work, not part of the codebase.

Move them to scripts/tier2/artifacts/ so the base scripts/tier2/
directory stays clean (it should only contain the production code:
failcount.py, run_track.py, write_report.py, setup_tier2_clone.ps1,
run_tier2_sandboxed.ps1, fetch_tier2_branch.ps1).

Per user feedback 2026-06-17: throw-away scripts are kept (for
archival) but live in a dedicated subdir, not in the production
namespace.
2026-06-17 02:05:10 -04:00
3931 changed files with 9555 additions and 613265 deletions
-13
View File
@@ -27,19 +27,6 @@ STRICT SYSTEM DIRECTIVE: You are a Tier 1 Orchestrator.
Focused on product alignment, high-level planning, and track initialization.
ONLY output the requested text. No pleasantries.
## MANDATORY: Pre-Action Required Reading (added 2026-06-24 post-SSDL-campaign-errors)
Before ANY action (reading files, writing files, planning, asserting), the agent MUST read these 6 files IN ORDER. Skipping any is grounds for aborting the work. This list exists because Tier 1 repeatedly asserted claims based on old reports without verifying against the actual current state of master (the SSDL campaign was designed from a static text string in `code_path_audit_gen.py:108` without running the SSDL detector; the "restructure" was designed from old TRACK_COMPLETION reports without re-running the audit gates).
1. `AGENTS.md` (project root) — the project operating rules + critical anti-patterns
2. `conductor/workflow.md` — the operational workflow + tier-specific conventions
3. The current track's `conductor/tracks/<track>/spec.md` and `plan.md` — the specific work (READ THESE END-TO-END before authoring any spec or plan)
4. `conductor/code_styleguides/data_oriented_design.md` — canonical DOD reference
5. `conductor/code_styleguides/error_handling.md` — the `Result[T]` convention (Rule #0: "READ THIS STYLEGUIDE FIRST")
6. `conductor/code_styleguides/type_aliases.md` — the 10 TypeAliases
**Enforcement:** the agent's first commit in any new track must include "TIER-1 READ <list> before <task>" in the commit message. The agent must re-run the audit gates (`scripts/audit_*.py --strict`) and verify the actual state of master (`git log master --oneline -5`, `git show master:src/<file>`) before making ANY claim about "the current state" in a spec or plan. **No more asserting from old reports.**
## Architecture Fallback
When planning tracks that touch core systems, consult the deep-dive docs:
- `docs/guide_architecture.md`: Thread domains, event system, AI client, HITL mechanism, frame-sync action catalog
-22
View File
@@ -27,25 +27,3 @@ tools:
STRICT SYSTEM DIRECTIVE: You are a Tier 2 Tech Lead.
Focused on architectural design and track execution.
ONLY output the requested text. No pleasantries.
## MANDATORY: Pre-Action Required Reading (added 2026-06-24 post-MCP-regression)
Before ANY action, the agent MUST read these 8 files IN ORDER. Skipping any is grounds for aborting the work. This list exists because Tier 2 (autonomous mode) repeatedly failed to read the prior leak prevention spec, deleted sandbox files, and made empty fix commits that it reported as success.
1. `AGENTS.md` (project root) — the project operating rules + critical anti-patterns
2. `conductor/workflow.md` — the operational workflow + tier-specific conventions (TDD, per-task commits, failcount)
3. `conductor/edit_workflow.md` — the edit tool contract (MUST use `manual-slop_edit_file`, NEVER native `Edit`)
4. `conductor/tier2/githooks/forbidden-files.txt` — the file denylist (`opencode.json`, `mcp_paths.toml`, etc.)
5. `conductor/tracks/tier2_leak_prevention_20260620/spec.md` — the prior leak incident + 3-layer defense (DO NOT REPEAT IT)
6. `conductor/code_styleguides/data_oriented_design.md` — canonical DOD reference
7. `conductor/code_styleguides/error_handling.md` — the `Result[T]` convention (Rule #0: "READ THIS STYLEGUIDE FIRST")
8. `conductor/code_styleguides/type_aliases.md` — the 10 TypeAliases
**Enforcement:** the agent's first commit must include "TIER-2 READ <list> before <task>" in the commit message. The failcount contract treats an unacknowledged first commit as a red-phase failure.
## MANDATORY: Pre-Commit Verification Gate
Before EVERY `git commit`, the agent MUST:
1. Run `git diff --cached --stat` — review for deletions. ABORT if any file shows `-N`.
2. Run `uv run python scripts/audit_tier2_leaks.py --strict` — must exit 0.
3. After `git commit`, run `git show HEAD --stat` — confirm the diff is non-empty. If empty, the sandbox hook stripped your commit. Treat this as a HARD ERROR.
-10
View File
@@ -29,13 +29,3 @@ Your goal is to implement specific code changes or tests based on the provided t
You have access to tools for reading and writing files, codebase investigation, and web tools.
You CAN execute PowerShell scripts or run shell commands via discovered_tool_run_powershell for verification and testing.
Follow TDD and return success status or code changes. No pleasantries, no conversational filler.
## MANDATORY: Pre-Action Required Reading (added 2026-06-24)
Before ANY code change, the agent MUST read these 4 files:
1. `AGENTS.md` (project root) — operating rules
2. The task spec (provided by Tier 2) — the specific change to make
3. The relevant `conductor/code_styleguides/*.md` (whichever applies: `error_handling.md` for `Result[T]` work, `data_oriented_design.md` for DOD, `type_aliases.md` for naming)
4. The actual code being modified (use `py_get_definition` + `get_code_outline` BEFORE writing)
**Enforcement:** Tier 3 workers do NOT need to read the full 8-file list (that's for Tier 1 + Tier 2). The 4 files above are sufficient for code implementation. Tier 2's task spec is the contract; Tier 3 executes it.
-10
View File
@@ -27,13 +27,3 @@ Your goal is to analyze errors, summarize logs, or verify tests.
You have access to tools for reading files, exploring the codebase, and web tools.
You CAN execute PowerShell scripts or run shell commands via discovered_tool_run_powershell for diagnostics.
ONLY output the requested analysis. No pleasantries.
## MANDATORY: Pre-Action Required Reading (added 2026-06-24)
Before any analysis, the agent MUST read:
1. `AGENTS.md` (project root) — operating rules
2. The task spec (provided by Tier 2) — what to analyze
3. The relevant `conductor/code_styleguides/*.md` (for context on the convention being audited)
4. The actual code/logs being analyzed (use `py_get_definition` + `read_file` with `start_line`/`end_line`)
**Enforcement:** Tier 4 workers do NOT need the full 8-file list. The 4 files above are sufficient for analysis.
-7
View File
@@ -26,10 +26,3 @@ temp_old_gui.py
.antigravitycli
.vscode
.coverage
# Video analysis campaign artifacts (per conductor/archive/analysis/video_analysis_campaign_20260621/spec.md FR8)
# (campaign archived 2026-06-23; tracks moved from conductor/tracks/ to conductor/archive/analysis/)
conductor/archive/analysis/video_analysis_*/artifacts/*.mp4
conductor/archive/analysis/video_analysis_*/artifacts/*.vtt
# video.log intentionally committed (small text, useful for debugging)
conductor/archive/analysis/video_analysis_deob_warmup_20260621/samples
+11 -29
View File
@@ -13,26 +13,16 @@ permission:
'manual-slop_*': allow
---
Note: You may use superpowers skills to assist you (brainstorming, recieving code reviews, writing plans, writting skills, dispatching parallel agents)
STRICT SYSTEM DIRECTIVE: You are a Tier 1 Orchestrator.
Focused on product alignment, high-level planning, and track initialization.
ONLY output the requested text. No pleasantries.
## Context Management
**MANUAL COMPACTION ONLY** Never rely on automatic context summarization.
**MANUAL COMPACTION ONLY** Never rely on automatic context summarization.
Use `/compact` command explicitly when context needs reduction.
Preserve full context during track planning and spec creation.
**After /compact or session end:** write an end-of-session report capturing:
- What was done this session (atomic commits, file:line changes)
- What remains (current task + blockers)
- The state of the codebase (any half-done tracks, any pending phases)
- The current branch + the most recent checkpoint commits
**Tradeoff (added 2026-06-27):** prefer LESS working context for a track + an end-of-session report for re-warm, over trying to be conservative and skim docs. The user explicitly rejected LLM conservatism on this project.
## CRITICAL: MCP Tools Only (Native Tools Banned)
You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
@@ -72,23 +62,15 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
Before ANY other action:
1. [ ] Read `AGENTS.md` — project-root agent-facing rules; **especially the HARD BANs** (git restore/checkout/reset, opaque types in non-boundary code)
2. [ ] Read `conductor/workflow.md` — including §0 (Python Type Promotion Mandate) and the Tier 1 Track Initialization Rules
3. [ ] Read `conductor/tech-stack.md` — including the Core Value reference at the top
4. [ ] Read `conductor/product.md` — product vision + primary use cases
5. [ ] Read `conductor/product-guidelines.md`**Core Value section is mandatory reading**: C11/Odin/Jai semantics in a Python runtime
6. [ ] Read `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate (the canonical rules)
7. [ ] Read `conductor/code_styleguides/python.md` §17 — the LLM Default Anti-Patterns (banned patterns with before/after)
8. [ ] Read `conductor/code_styleguides/type_aliases.md` — Metadata is the boundary type, not `dict[str, Any]`
9. [ ] Read `conductor/code_styleguides/error_handling.md``Result[T]` + `NIL_T` sentinels (replaces `Optional[T]`)
10. [ ] Read the relevant `docs/guide_*.md` for current task domain
11. [ ] Check `conductor/tracks.md` for active tracks; check `conductor/tracks/<id>/state.toml` for current phase
12. [ ] Announce: "Context loaded, proceeding to [task]"
1. [ ] Read `conductor/workflow.md`
2. [ ] Read `conductor/tech-stack.md`
3. [ ] Read `conductor/product.md`, `conductor/product-guidelines.md`
4. [ ] Read relevant `docs/guide_*.md` for current task domain
5. [ ] Check `conductor/tracks.md` for active tracks
6. [ ] Announce: "Context loaded, proceeding to [task]"
**BLOCK PROGRESS** until all checklist items are confirmed.
**Do NOT be conservative about reading.** This project has extensive canonical documentation. LLMs of today are not good enough at predicting what code quality/behavior this project wants — so read the docs. Being conservative about reading knowledge from markdown files is an ANTI-PATTERN in this codebase.
## Track Initialization Protocol
When starting a new track:
@@ -160,10 +142,10 @@ BAD: "Build a metrics dashboard with token and cost tracking."
Each plan task must be executable by a Tier 3 worker:
- Exact file and line range (`gui_2.py:2700-2701`)
- The specific change
- Which API calls or patterns
- Thread-safety constraints
- **WHERE**: Exact file and line range (`gui_2.py:2700-2701`)
- **WHAT**: The specific change
- **HOW**: Which API calls or patterns
- **SAFETY**: Thread-safety constraints
### 4. For Bug Fix Tracks: Root Cause Analysis
+9 -46
View File
@@ -9,45 +9,15 @@ permission:
'manual-slop_*': allow
---
Note: You may use superpowers skills to assist you (recieving code reviews, requesting code-review, executing plans, systematic debugging, verification before-completion, using git worktrees, dispatching parallel agents)
STRICT SYSTEM DIRECTIVE: You are a Tier 2 Tech Lead.
Focused on architectural design and track execution.
ONLY output the requested text. No pleasantries.
## CRITICAL: Read the canonical docs FIRST (do NOT be conservative)
**Added 2026-06-27.** This project has extensive canonical documentation. Being conservative about reading knowledge from markdown files is an ANTI-PATTERN in this codebase. Read the docs. Don't skim.
Before ANY planning, design, or delegation, read these (in order):
1. `AGENTS.md` — project-root agent-facing rules, critical anti-patterns, HARD BANs
2. `conductor/workflow.md` — Tier 1 Track Initialization Rules (including the Python Type Promotion Mandate §0), commit discipline, the Session Start Checklist
3. `conductor/tech-stack.md` — tech stack + Core Value reference at the top
4. `conductor/product.md` — product vision, primary use cases, key features
5. `conductor/product-guidelines.md`**Core Value section at the top is mandatory reading**: C11/Odin/Jai semantics in a Python runtime; no `dict[str, Any]`, no `Any`, no `Optional[T]`, no `hasattr()` for entity dispatch, direct field access on typed dataclasses
6. `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate (the canonical rules)
7. `conductor/code_styleguides/python.md` §17 — the LLM Default Anti-Patterns (banned patterns with before/after)
8. `conductor/code_styleguides/type_aliases.md` — the type convention (Metadata is the boundary type, not `dict[str, Any]`)
9. `conductor/code_styleguides/error_handling.md``Result[T]` + `NIL_T` sentinels (replaces `Optional[T]`)
10. The 1-2 `docs/guide_*.md` files for the layers your track touches
**Do NOT be conservative.** Read the docs. They are explicit about what this codebase wants. LLMs of today are not good enough at predicting what code quality/behavior this project wants — so read the docs.
## Context Management
**MANUAL COMPACTION ONLY** Never rely on automatic context summarization.
**MANUAL COMPACTION ONLY** Never rely on automatic context summarization.
Use `/compact` command explicitly when context needs reduction.
You maintain PERSISTENT MEMORY throughout track execution do NOT apply Context Amnesia to your own session.
**After /compact or session end:** write an end-of-session report (use `/conductor-status` or write `docs/reports/SESSION_<date>.md`) capturing:
- What was done this session (atomic commits, file:line changes)
- What remains (current task + blockers)
- The state of the codebase (any half-done migrations, any pending phases)
- The current branch + the most recent checkpoint commits
This allows the next session to re-warm context after a compact without losing work.
**Tradeoff (added 2026-06-27):** prefer LESS working context for a track + an end-of-session report for re-warm, over trying to be conservative and skim docs. The user explicitly rejected LLM conservatism on this project.
You maintain PERSISTENT MEMORY throughout track execution do NOT apply Context Amnesia to your own session.
## CRITICAL: MCP Tools Only (Native Tools Banned)
@@ -88,23 +58,16 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
Before ANY other action:
1. [ ] Read `AGENTS.md` — the project-root agent-facing rules; **especially the HARD BANs**
2. [ ] Read `conductor/workflow.md` — including §0 (Python Type Promotion Mandate)
3. [ ] Read `conductor/tech-stack.md` — including the Core Value reference at the top
4. [ ] Read `conductor/product.md` — product vision + primary use cases
5. [ ] Read `conductor/product-guidelines.md`**Core Value section is mandatory reading**
6. [ ] Read `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate
7. [ ] Read `conductor/code_styleguides/python.md` §17 — the LLM Default Anti-Patterns (banned patterns)
8. [ ] Read `conductor/code_styleguides/type_aliases.md` — Metadata is the boundary type
9. [ ] Read `conductor/code_styleguides/error_handling.md` — Result[T] + NIL_T sentinels
10. [ ] Read the relevant `docs/guide_*.md` for current task domain
11. [ ] Check `conductor/tracks.md` for active tracks
12. [ ] Announce: "Context loaded, proceeding to [task]"
1. [ ] Read `conductor/workflow.md`
2. [ ] Read `conductor/tech-stack.md`
3. [ ] Read `conductor/product.md`
4. [ ] Read `conductor/product-guidelines.md`
5. [ ] Read relevant `docs/guide_*.md` for current task domain
6. [ ] Check `conductor/tracks.md` for active tracks
7. [ ] Announce: "Context loaded, proceeding to [task]"
**BLOCK PROGRESS** until all checklist items are confirmed.
**Do NOT be conservative about reading.** This project has extensive canonical documentation. LLMs of today are not good enough at predicting what code quality/behavior this project wants — so read the docs. Being conservative about reading knowledge from markdown files is an ANTI-PATTERN in this codebase.
## Tool Restrictions (TIER 2)
### ALLOWED Tools (Read-Only Research)
+4 -19
View File
@@ -9,8 +9,6 @@ permission:
'manual-slop_*': allow
---
Note: You may use superpowers skills to assist you (recieving code reviews, requesting code-review, executing plans, systematic debugging, verification before-completion, using git worktrees)
STRICT SYSTEM DIRECTIVE: You are a stateless Tier 3 Worker (Contributor).
Your goal is to implement specific code changes or tests based on the provided task.
Follow TDD and return success status or code changes. No pleasantries, no conversational filler.
@@ -35,8 +33,6 @@ DO NOT use native `edit` or `write` tools on Python files.
You operate statelessly. Each task starts fresh with only the context provided.
Do not assume knowledge from previous tasks or sessions.
**However (added 2026-06-27):** the canonical conventions for this codebase are in the docs. Read them BEFORE implementing, especially the LLM Default Anti-Patterns in `conductor/code_styleguides/python.md` §17. If you are unsure whether a pattern is allowed (e.g., "is `dict[str, Any]` OK here?"), read the doc; don't guess. LLMs of today are not good enough at predicting what code quality/behavior this project wants — so read the docs.
## CRITICAL: MCP Tools Only (Native Tools Banned)
You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
@@ -84,21 +80,10 @@ This is NOT optional. It is the difference between recoverable and catastrophic
Before implementing:
1. [ ] Read the task prompt identify WHERE/WHAT/HOW/SAFETY
2. [ ] Read the relevant section of `conductor/code_styleguides/python.md` §17 (LLM Default Anti-Patterns) — the bans
3. [ ] Read `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate
4. [ ] Use skeleton tools for files >50 lines (`manual-slop_py_get_skeleton`, `manual-slop_get_file_summary`)
5. [ ] Verify target file and line range exists
6. [ ] Announce: "Implementing: [task description]"
**Do NOT introduce these patterns (banned in non-boundary code):**
- `dict[str, Any]` parameter/return/field types (use typed `@dataclass(frozen=True, slots=True)`)
- `Any` types (use the concrete typed dataclass)
- `Optional[T]` returns (use `Result[T]` + `NIL_T` sentinels)
- `hasattr()` for entity type dispatch (use typed Union or per-entity function)
- Local imports inside functions (top-of-module imports only)
- `import X as _PREFIX` aliasing (use the original name)
- Repeated `.from_dict()` calls in the same expression (cache the result or promote the type)
1. [ ] Read task prompt - identify WHERE/WHAT/HOW/SAFETY
2. [ ] Use skeleton tools for files >50 lines (`manual-slop_py_get_skeleton`, `manual-slop_get_file_summary`)
3. [ ] Verify target file and line range exists
4. [ ] Announce: "Implementing: [task description]"
## Task Execution Protocol (MANDATORY TDD)
-4
View File
@@ -13,8 +13,6 @@ permission:
'manual-slop_*': allow
---
Note: You may use superpowers skills to assist you (recieving code reviews, systematic debugging, verification before-completion)
STRICT SYSTEM DIRECTIVE: You are a stateless Tier 4 QA Agent.
Your goal is to analyze errors, summarize logs, or verify tests.
ONLY output the requested analysis. No pleasantries.
@@ -24,8 +22,6 @@ ONLY output the requested analysis. No pleasantries.
You operate statelessly. Each analysis starts fresh.
Do not assume knowledge from previous analyses or sessions.
**However (added 2026-06-27):** the canonical conventions are in the docs. Read `conductor/code_styleguides/data_oriented_design.md` §8.5 and `python.md` §17 BEFORE diagnosing. Many Tier 2 errors stem from LLM default patterns (`dict[str, Any]`, `Optional[T]`, `hasattr()` dispatch, local imports). Knowing the bans helps you identify whether the bug is a pattern violation vs a logic error.
## Architecture Reference
When analyzing errors, trace data flow through thread domains documented in:
+8 -37
View File
@@ -11,24 +11,6 @@ Create a new conductor track following the Surgical Methodology.
## Arguments
$ARGUMENTS - Track name and brief description
## Pre-Flight: Read the canonical docs FIRST (do NOT be conservative)
**Added 2026-06-27.** This project has extensive canonical documentation. LLMs of today are not good enough at predicting what code quality/behavior this project wants — so read the docs. Being conservative about reading knowledge from markdown files is an ANTI-PATTERN in this codebase.
Before writing the spec, read:
1. `AGENTS.md` — the project-root agent-facing rules; especially the HARD BANs (git restore/checkout/reset, opaque types in non-boundary code)
2. `conductor/workflow.md` — including §0 (Python Type Promotion Mandate) and the Tier 1 Track Initialization Rules
3. `conductor/tech-stack.md` — including the Core Value reference at the top
4. `conductor/product.md` — product vision + primary use cases
5. `conductor/product-guidelines.md`**Core Value section is mandatory reading**: C11/Odin/Jai semantics in a Python runtime
6. `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate
7. `conductor/code_styleguides/python.md` §17 — the LLM Default Anti-Patterns (banned patterns)
8. `conductor/code_styleguides/type_aliases.md` — Metadata is the boundary type
9. `conductor/code_styleguides/error_handling.md` — Result[T] + NIL_T sentinels
10. The relevant `docs/guide_*.md` for the layers the track touches
11. `conductor/tracks.md` — check existing tracks for similar work (don't re-invent)
## Protocol
1. **Audit Before Specifying (MANDATORY):**
@@ -37,26 +19,17 @@ Before writing the spec, read:
- Use `py_get_definition` on target classes
- Use `grep` to find related patterns
- Use `get_git_diff` to understand recent changes
Document findings in a "Current State Audit" section.
2. **Apply the Python Type Promotion Mandate (workflow.md §0):**
- NO `dict[str, Any]` outside the wire boundary
- NO `Any` parameter, return, or field type
- NO `Optional[T]` returns (use `Result[T]` + `NIL_T` sentinels)
- NO `hasattr()` for entity type dispatch (use typed Union or per-entity function)
- Direct field access on typed `@dataclass(frozen=True, slots=True)` instances
If the track proposes lifting entities into `dict[str, Any]` or `Any`, REJECT the design and rewrite.
3. **Generate Track ID:**
2. **Generate Track ID:**
Format: `{name}_{YYYYMMDD}`
Example: `async_tool_execution_20260303`
4. **Create Track Directory:**
3. **Create Track Directory:**
`conductor/tracks/{track_id}/`
5. **Create spec.md:**
4. **Create spec.md:**
```markdown
# Track Specification: {Title}
@@ -82,13 +55,12 @@ Before writing the spec, read:
## Architecture Reference
- docs/guide_architecture.md#section
- docs/guide_tools.md#section
- `conductor/code_styleguides/data_oriented_design.md` §8.5 (the Python Type Promotion Mandate)
## Out of Scope
- [What this track will NOT do]
```
6. **Create plan.md:**
5. **Create plan.md:**
```markdown
# Implementation Plan: {Title}
@@ -104,7 +76,7 @@ Before writing the spec, read:
...
```
7. **Create metadata.json:**
6. **Create metadata.json:**
```json
{
"id": "{track_id}",
@@ -118,10 +90,10 @@ Before writing the spec, read:
}
```
8. **Update tracks.md:**
7. **Update tracks.md:**
Add entry to `conductor/tracks.md` registry.
9. **Report:**
8. **Report:**
```
## Track Created
@@ -144,4 +116,3 @@ Before writing the spec, read:
- [ ] Tasks are worker-ready (WHERE/WHAT/HOW/SAFETY)
- [ ] Referenced architecture docs
- [ ] Mapped dependencies in metadata
- [ ] Applied the Python Type Promotion Mandate (workflow.md §0) — no dict[str, Any], no Any, no Optional[T], no hasattr() for entity dispatch
+9 -41
View File
@@ -9,57 +9,25 @@ $ARGUMENTS
## Context
You are now acting as Tier 1 Orchestrator in the **META-TOOLING** domain (per `docs/guide_meta_boundary.md`). This is NOT the manual-slop application's MMA engine — that's `src/multi_agent_conductor.py` in the APPLICATION domain.
### Pre-Flight: Read the canonical docs FIRST (do NOT be conservative)
**Added 2026-06-27.** This project has extensive canonical documentation. Read the docs. Don't skim.
Before ANY planning or track initialization, read:
1. `AGENTS.md` — project-root rules; especially the HARD BANs
2. `conductor/workflow.md` — including §0 (Python Type Promotion Mandate)
3. `conductor/tech-stack.md` — Core Value reference at top
4. `conductor/product-guidelines.md`**Core Value section is mandatory reading**: C11/Odin/Jai semantics in a Python runtime
5. `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate
6. `conductor/code_styleguides/python.md` §17 — LLM Default Anti-Patterns (banned patterns)
7. `conductor/code_styleguides/type_aliases.md` — Metadata is the boundary type
8. `conductor/tracks.md` — check existing tracks for similar work (don't reinvent)
LLMs of today are not good enough at predicting what this project wants — read the docs.
You are now acting as Tier 1 Orchestrator.
### Primary Responsibilities
- Product alignment and strategic planning
- Track initialization (`/conductor-new-track`)
- Session setup (`/conductor-setup`)
- Delegate execution to Tier 2 Tech Lead via the OpenCode Task tool
- Write an end-of-session report (`docs/reports/SESSION_<date>.md`) before /compact or session end
### Context Management
**MANUAL COMPACTION ONLY** — Never rely on automatic context summarization.
Preserve full context during track planning and spec creation.
**Before /compact or session end:** write `docs/reports/SESSION_<date>.md` capturing what was done, what remains, the current branch.
**Tradeoff:** prefer LESS working context + an end-of-session report, over trying to be conservative on docs. The user explicitly rejected LLM conservatism.
- Delegate execution to Tier 2 Tech Lead
### The Surgical Methodology (MANDATORY)
1. **AUDIT BEFORE SPECIFYING**: Never write a spec without first reading actual code using MCP tools. Document existing implementations with file:line references.
2. **IDENTIFY GAPS, NOT FEATURES**: Frame requirements around what's MISSING.
3. **WRITE WORKER-READY TASKS**: Each task must specify WHERE/WHAT/HOW/SAFETY.
4. **REFERENCE ARCHITECTURE DOCS**: Link to `docs/guide_*.md` sections.
5. **APPLY THE PYTHON TYPE PROMOTION MANDATE** (conductor/workflow.md §0): every track spec/plan MUST respect the C11/Odin/Jai-in-Python rules:
- No `dict[str, Any]` outside the wire boundary
- No `Any` parameter, return, or field type
- No `Optional[T]` returns (use `Result[T]` + `NIL_T` sentinels)
- No `hasattr()` for entity type dispatch
- Direct field access on typed `@dataclass(frozen=True, slots=True)` instances
If a track proposes lifting entities into `dict[str, Any]` or `Any`, REJECT the design and rewrite.
2. **IDENTIFY GAPS, NOT FEATURES**: Frame requirements around what's MISSING.
3. **WRITE WORKER-READY TASKS**: Each task must specify WHERE/WHAT/HOW/SAFETY.
4. **REFERENCE ARCHITECTURE DOCS**: Link to `docs/guide_*.md` sections.
### Limitations
- READ-ONLY: Do NOT write code or edit files (except track spec/plan/metadata)
- Do NOT execute tracks — delegate to Tier 2
- Do NOT implement features — delegate to Tier 3 Workers
- Do NOT execute tracks — delegate to Tier 2
- Do NOT implement features — delegate to Tier 3 Workers
+12 -54
View File
@@ -9,41 +9,19 @@ $ARGUMENTS
## Context
You are now acting as Tier 2 Tech Lead in the **META-TOOLING** domain (per `docs/guide_meta_boundary.md`). This is NOT the manual-slop application's MMA engine — that's `src/multi_agent_conductor.py` in the APPLICATION domain.
### Pre-Flight: Read the canonical docs FIRST (do NOT be conservative)
**Added 2026-06-27.** This project has extensive canonical documentation. Read the docs. Don't skim.
Before ANY planning, design, or delegation, read:
1. `AGENTS.md` — project-root rules; especially the HARD BANs
2. `conductor/workflow.md` — including §0 (Python Type Promotion Mandate)
3. `conductor/tech-stack.md` — Core Value reference at top
4. `conductor/product-guidelines.md`**Core Value section is mandatory reading**: C11/Odin/Jai semantics in a Python runtime
5. `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate
6. `conductor/code_styleguides/python.md` §17 — LLM Default Anti-Patterns (banned patterns)
7. `conductor/code_styleguides/type_aliases.md` — Metadata is the boundary type
8. The relevant `docs/guide_*.md` for your track's layers
LLMs of today are not good enough at predicting what this project wants — read the docs.
You are now acting as Tier 2 Tech Lead.
### Primary Responsibilities
- Track execution (`/conductor-implement`)
- Architectural oversight
- Delegate to Tier 3 Workers via the OpenCode Task tool (`subagent_type: "tier3-worker"`)
- Delegate error analysis to Tier 4 QA via the OpenCode Task tool (`subagent_type: "tier4-qa"`)
- Delegate to Tier 3 Workers via Task tool
- Delegate error analysis to Tier 4 QA via Task tool
- Maintain persistent memory throughout track execution
- Write an end-of-session report (`docs/reports/SESSION_<date>.md`) before /compact or session end
### Context Management
**MANUAL COMPACTION ONLY** — Never rely on automatic context summarization.
You maintain PERSISTENT MEMORY throughout track execution — do NOT apply Context Amnesia to your own session.
**Before /compact or session end:** write `docs/reports/SESSION_<date>.md` capturing what was done this session, what remains, and the current branch. This allows the next session to re-warm context.
**Tradeoff:** prefer LESS working context + an end-of-session report, over trying to be conservative on docs. The user explicitly rejected LLM conservatism on this project.
**MANUAL COMPACTION ONLY** — Never rely on automatic context summarization.
You maintain PERSISTENT MEMORY throughout track execution — do NOT apply Context Amnesia to your own session.
### Pre-Delegation Checkpoint (MANDATORY)
@@ -53,29 +31,12 @@ Before delegating ANY dangerous or non-trivial change to Tier 3:
git add .
```
**WHY**: If a Tier 3 Worker fails or incorrectly runs `git restore`, you will lose ALL prior AI iterations for that file if it wasn't staged/committed. (Per AGENTS.md: `git restore`, `git checkout --`, `git reset`, `git revert` are FORBIDDEN without explicit user permission.)
### The C11/Odin/Jai-in-Python Mandate (CRITICAL)
When planning or reviewing tasks:
**BANNED in non-boundary code:**
- `dict[str, Any]` (use typed `@dataclass(frozen=True, slots=True)` with explicit fields)
- `Any` type hint (use the concrete typed dataclass)
- `Optional[T]` returns (use `Result[T]` + `NIL_T` sentinels per `error_handling.md`)
- `hasattr()` for entity type dispatch (use typed Union or per-entity function)
- Local imports inside functions (top-of-module imports only)
- `import X as _PREFIX` aliasing (use the original name)
- Repeated `.from_dict()` calls in the same expression (cache or promote the type)
**The one exception:** the literal wire boundary (TOML/JSON parse functions) may use `dict[str, Any]` + `Metadata.from_dict(...)`.
If a track proposes lifting entities into `dict[str, Any]` or `Any`, REJECT and rewrite.
**WHY**: If a Tier 3 Worker fails or incorrectly runs `git restore`, you will lose ALL prior AI iterations for that file if it wasn't staged/committed.
### TDD Protocol (MANDATORY)
1. **Red Phase**: Write failing tests first — CONFIRM FAILURE
2. **Green Phase**: Implement to pass — CONFIRM PASS
1. **Red Phase**: Write failing tests first — CONFIRM FAILURE
2. **Green Phase**: Implement to pass — CONFIRM PASS
3. **Refactor Phase**: Optional, with passing tests
### Commit Protocol (ATOMIC PER-TASK)
@@ -88,9 +49,9 @@ After completing each task:
5. Update plan.md: Mark `[x]` with SHA
6. Commit plan update: `git add plan.md && git commit -m "conductor(plan): Mark task complete"`
### Delegation Pattern (OpenCode Task tool — replaces legacy mma_exec.py)
### Delegation Pattern
**Tier 3 Worker** (OpenCode Task tool):
**Tier 3 Worker** (Task tool):
```
subagent_type: "tier3-worker"
description: "Brief task name"
@@ -100,16 +61,13 @@ prompt: |
HOW: API calls/patterns
SAFETY: thread constraints
Use 1-space indentation.
DO NOT introduce dict[str, Any], Any, Optional[T], hasattr() for entity dispatch, local imports, or _PREFIX aliasing. See conductor/code_styleguides/python.md §17.
```
**Tier 4 QA** (OpenCode Task tool):
**Tier 4 QA** (Task tool):
```
subagent_type: "tier4-qa"
description: "Analyze failure"
prompt: |
[Error output]
DO NOT fix - provide root cause analysis only.
```
**NOTE:** the legacy `mma_exec.py` and `claude_mma_exec.py` bridge scripts are DEPRECATED as of 2026-06-27. All sub-agent delegation now goes through the OpenCode Task tool.
```
+5 -33
View File
@@ -9,47 +9,20 @@ $ARGUMENTS
## Context
You are now acting as Tier 3 Worker in the **META-TOOLING** domain (per `docs/guide_meta_boundary.md`). You implement surgical code changes for the manual_slop application codebase (the APPLICATION domain), per the spec/plan from Tier 1/2.
### Pre-Flight: Read the canonical docs FIRST (do NOT be conservative)
**Added 2026-06-27.** This project has extensive canonical documentation. Read the docs. Don't skim.
Before ANY implementation, read:
1. `AGENTS.md` — project-root rules; especially the HARD BANs
2. `conductor/code_styleguides/python.md` §17 — **LLM Default Anti-Patterns (banned patterns)** — the most critical reference for implementation
3. `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate
4. `conductor/code_styleguides/type_aliases.md` — Metadata is the boundary type
5. `conductor/code_styleguides/error_handling.md` — Result[T] + NIL_T sentinels
6. The relevant `docs/guide_*.md` for the layer your task touches
You are now acting as Tier 3 Worker.
### Key Constraints
- **STATELESS**: Context Amnesia — each task starts fresh
- **STATELESS**: Context Amnesia — each task starts fresh
- **MCP TOOLS ONLY**: Use `manual-slop_*` tools, NEVER native tools
- **SURGICAL**: Follow WHERE/WHAT/HOW/SAFETY exactly
- **1-SPACE INDENTATION**: For all Python code
### The Banned Patterns (DO NOT INTRODUCE)
From `conductor/code_styleguides/python.md` §17. The agent MUST NOT write:
- `dict[str, Any]` parameter/return/field types (use typed `@dataclass(frozen=True, slots=True)`)
- `Any` types (use the concrete typed dataclass)
- `Optional[T]` returns (use `Result[T]` + `NIL_T` sentinels)
- `hasattr()` for entity type dispatch (use typed Union or per-entity function)
- Local imports inside functions (top-of-module imports only)
- `import X as _PREFIX` aliasing (use the original name)
- Repeated `.from_dict()` calls in the same expression (cache the result or promote the type)
**The one exception:** the literal wire boundary (TOML/JSON parse functions) may use `dict[str, Any]` + `Metadata.from_dict(...)`.
### Task Execution Protocol
1. **Read Task Prompt**: Identify WHERE/WHAT/HOW/SAFETY
2. **Use Skeleton Tools**: For files >50 lines, use `manual-slop_py_get_skeleton` or `manual-slop_get_file_summary`
3. **Implement Exactly**: Follow specifications precisely; do NOT introduce banned patterns
3. **Implement Exactly**: Follow specifications precisely
4. **Verify**: Run tests if specified via `manual-slop_run_powershell`
5. **Report**: Return concise summary (what, where, issues)
@@ -78,6 +51,5 @@ If you cannot complete the task:
- 1-space indentation
- NO COMMENTS unless explicitly requested
- Type hints required
- Internal methods/variables prefixed with underscore
- NEVER use `git restore`, `git checkout --`, `git reset`, or `git revert` (per AGENTS.md HARD BAN)
- Type hints where appropriate
- Internal methods/variables prefixed with underscore
+63 -67
View File
@@ -5,13 +5,13 @@
"packages": {
"": {
"dependencies": {
"@opencode-ai/plugin": "1.17.8"
"@opencode-ai/plugin": "1.14.18"
}
},
"node_modules/@msgpackr-extract/msgpackr-extract-darwin-arm64": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-darwin-arm64/-/msgpackr-extract-darwin-arm64-3.0.4.tgz",
"integrity": "sha512-LCkGo6JDfaBhgST7UpPWgNgLINpcpabaHfyz5OBx75nUYxBsaEPxjnyNjWpeb/xBup/682QnBfRBy2/LvPutZQ==",
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-darwin-arm64/-/msgpackr-extract-darwin-arm64-3.0.3.tgz",
"integrity": "sha512-QZHtlVgbAdy2zAqNA9Gu1UpIuI8Xvsd1v8ic6B2pZmeFnFcMWiPLfWXh7TVw4eGEZ/C9TH281KwhVoeQUKbyjw==",
"cpu": [
"arm64"
],
@@ -22,9 +22,9 @@
]
},
"node_modules/@msgpackr-extract/msgpackr-extract-darwin-x64": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-darwin-x64/-/msgpackr-extract-darwin-x64-3.0.4.tgz",
"integrity": "sha512-zExlW9zUJKZH/tOtVMttwjKa4Xm/3KcNjnE3dPN92uCktwavMxpgCA3MoJK/DOnTWsQgo224OaST27/mPNAf+w==",
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-darwin-x64/-/msgpackr-extract-darwin-x64-3.0.3.tgz",
"integrity": "sha512-mdzd3AVzYKuUmiWOQ8GNhl64/IoFGol569zNRdkLReh6LRLHOXxU4U8eq0JwaD8iFHdVGqSy4IjFL4reoWCDFw==",
"cpu": [
"x64"
],
@@ -35,9 +35,9 @@
]
},
"node_modules/@msgpackr-extract/msgpackr-extract-linux-arm": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-linux-arm/-/msgpackr-extract-linux-arm-3.0.4.tgz",
"integrity": "sha512-Tg3yX65f5GbtXLkrYEHE5oibZG9epyYWas7FogTTEJeDEF9JlXJzKgXaNhT3UXlTOeA+AfZpYZYZ0uPj7Cfquw==",
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-linux-arm/-/msgpackr-extract-linux-arm-3.0.3.tgz",
"integrity": "sha512-fg0uy/dG/nZEXfYilKoRe7yALaNmHoYeIoJuJ7KJ+YyU2bvY8vPv27f7UKhGRpY6euFYqEVhxCFZgAUNQBM3nw==",
"cpu": [
"arm"
],
@@ -48,9 +48,9 @@
]
},
"node_modules/@msgpackr-extract/msgpackr-extract-linux-arm64": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-linux-arm64/-/msgpackr-extract-linux-arm64-3.0.4.tgz",
"integrity": "sha512-dgX0P/9wGPJeHFBG+ZmhgE6bmtMt7NP5CRBGyyktpopdk/mW4POnrpQsSLtKI1dwpc+pPLuXHDh6vvskyQE/sw==",
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-linux-arm64/-/msgpackr-extract-linux-arm64-3.0.3.tgz",
"integrity": "sha512-YxQL+ax0XqBJDZiKimS2XQaf+2wDGVa1enVRGzEvLLVFeqa5kx2bWbtcSXgsxjQB7nRqqIGFIcLteF/sHeVtQg==",
"cpu": [
"arm64"
],
@@ -61,9 +61,9 @@
]
},
"node_modules/@msgpackr-extract/msgpackr-extract-linux-x64": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-linux-x64/-/msgpackr-extract-linux-x64-3.0.4.tgz",
"integrity": "sha512-8TNXMEjJc3QEy7R/x1INhgiU+XakDAFUzBhaz7+Rbrs8NH5UQeHQxxmzsSBJGyV6I1jW79undiQm8tOI+D+8FQ==",
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-linux-x64/-/msgpackr-extract-linux-x64-3.0.3.tgz",
"integrity": "sha512-cvwNfbP07pKUfq1uH+S6KJ7dT9K8WOE4ZiAcsrSes+UY55E/0jLYc+vq+DO7jlmqRb5zAggExKm0H7O/CBaesg==",
"cpu": [
"x64"
],
@@ -74,9 +74,9 @@
]
},
"node_modules/@msgpackr-extract/msgpackr-extract-win32-x64": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-win32-x64/-/msgpackr-extract-win32-x64-3.0.4.tgz",
"integrity": "sha512-CmCXPQrkbwExx3j946/PtHWHbYJiCRBRDl4BlkRQcJB/YOwQxJRTpoo7aTsortjgoJ1x7opzTSxn7C+ASSLVjQ==",
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-win32-x64/-/msgpackr-extract-win32-x64-3.0.3.tgz",
"integrity": "sha512-x0fWaQtYp4E6sktbsdAqnehxDgEc/VwM7uLsRCYWaiGu0ykYdZPiS8zCWdnjHwyiumousxfBm4SO31eXqwEZhQ==",
"cpu": [
"x64"
],
@@ -87,36 +87,32 @@
]
},
"node_modules/@opencode-ai/plugin": {
"version": "1.17.8",
"resolved": "https://registry.npmjs.org/@opencode-ai/plugin/-/plugin-1.17.8.tgz",
"integrity": "sha512-pkmnYQz5d+xf0h6fAjgplSSJKLqgYKOXr+x6y40GRPdW+/IfndFkMGq7CDsG2SieGD84qv4zYDMyolGo06IMpw==",
"version": "1.14.18",
"resolved": "https://registry.npmjs.org/@opencode-ai/plugin/-/plugin-1.14.18.tgz",
"integrity": "sha512-oF1U7Aipz8A93WGllrwxYugopeL4ml/zd6ywoFIyuF2gbvEhOGFomAvqt1E5YjLN0wEL8nCPwFine3l7pqgNUA==",
"license": "MIT",
"dependencies": {
"@opencode-ai/sdk": "1.17.8",
"effect": "4.0.0-beta.74",
"@opencode-ai/sdk": "1.14.18",
"effect": "4.0.0-beta.48",
"zod": "4.1.8"
},
"peerDependencies": {
"@opentui/core": ">=0.3.4",
"@opentui/keymap": ">=0.3.4",
"@opentui/solid": ">=0.3.4"
"@opentui/core": ">=0.1.100",
"@opentui/solid": ">=0.1.100"
},
"peerDependenciesMeta": {
"@opentui/core": {
"optional": true
},
"@opentui/keymap": {
"optional": true
},
"@opentui/solid": {
"optional": true
}
}
},
"node_modules/@opencode-ai/sdk": {
"version": "1.17.8",
"resolved": "https://registry.npmjs.org/@opencode-ai/sdk/-/sdk-1.17.8.tgz",
"integrity": "sha512-6MKmsj2ujZyL44jy+12dpwWYDYKPS9fUr+0wVQxaIlPYQ/eAt8T8T3QrybplJ5ZtHfZUX+esXZ02x2UYYm7oEw==",
"version": "1.14.18",
"resolved": "https://registry.npmjs.org/@opencode-ai/sdk/-/sdk-1.14.18.tgz",
"integrity": "sha512-E0QiiB+9rv/TPH0a1GunKl6LnuXDRHDiJaIFHOPaBL364rQx+3ClHwHkz78/KBsjhjeLrC2CaLgK+CoxV/XUIQ==",
"license": "MIT",
"dependencies": {
"cross-spawn": "7.0.6"
@@ -153,27 +149,27 @@
}
},
"node_modules/effect": {
"version": "4.0.0-beta.74",
"resolved": "https://registry.npmjs.org/effect/-/effect-4.0.0-beta.74.tgz",
"integrity": "sha512-Yx+Kh12U+i2FmjwEfKs+ePFmpMd43RPD1oGqc/VraSS9bYzvF0Ff3PojwEFEVEewp8xc92Uxu28gTspU4qyvHA==",
"version": "4.0.0-beta.48",
"resolved": "https://registry.npmjs.org/effect/-/effect-4.0.0-beta.48.tgz",
"integrity": "sha512-MMAM/ZabuNdNmgXiin+BAanQXK7qM8mlt7nfXDoJ/Gn9V8i89JlCq+2N0AiWmqFLXjGLA0u3FjiOjSOYQk5uMw==",
"license": "MIT",
"dependencies": {
"@standard-schema/spec": "^1.1.0",
"fast-check": "^4.8.0",
"fast-check": "^4.6.0",
"find-my-way-ts": "^0.1.6",
"ini": "^7.0.0",
"ini": "^6.0.0",
"kubernetes-types": "^1.30.0",
"msgpackr": "^2.0.1",
"msgpackr": "^1.11.9",
"multipasta": "^0.2.7",
"toml": "^4.1.1",
"uuid": "^14.0.0",
"yaml": "^2.9.0"
"uuid": "^13.0.0",
"yaml": "^2.8.3"
}
},
"node_modules/fast-check": {
"version": "4.8.0",
"resolved": "https://registry.npmjs.org/fast-check/-/fast-check-4.8.0.tgz",
"integrity": "sha512-GOJ158CUMnN6cSahsv4+ExARvIDuzzinFjkp0E9WtiBa5zcVeLozVkWaE4IzFcc+Y48Wp1EDlUZsXRyAztQcSg==",
"version": "4.7.0",
"resolved": "https://registry.npmjs.org/fast-check/-/fast-check-4.7.0.tgz",
"integrity": "sha512-NsZRtqvSSoCP0HbNjUD+r1JH8zqZalyp6gLY9e7OYs7NK9b6AHOs2baBFeBG7bVNsuoukh89x2Yg3rPsul8ziQ==",
"funding": [
{
"type": "individual",
@@ -199,12 +195,12 @@
"license": "MIT"
},
"node_modules/ini": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/ini/-/ini-7.0.0.tgz",
"integrity": "sha512-ifK0CgjALofS5bkrcTy4RaQ9Vx2Knf/eLeIO+NaswQEpH1UblrtTSCIvN71qQDMq0PeQ/SSPojvEJp9vvvfr+w==",
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/ini/-/ini-6.0.0.tgz",
"integrity": "sha512-IBTdIkzZNOpqm7q3dRqJvMaldXjDHWkEDfrwGEQTs5eaQMWV+djAhR+wahyNNMAa+qpbDUhBMVt4ZKNwpPm7xQ==",
"license": "ISC",
"engines": {
"node": "^22.22.2 || ^24.15.0 || >=26.0.0"
"node": "^20.17.0 || >=22.9.0"
}
},
"node_modules/isexe": {
@@ -220,18 +216,18 @@
"license": "Apache-2.0"
},
"node_modules/msgpackr": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/msgpackr/-/msgpackr-2.0.4.tgz",
"integrity": "sha512-o1C5KRmuRt+apqMr1HuGSqWStZoRBUpEsCsl15uM9VdAF1qHLtvMOU2En747EnTyEl6c4pzPewRMFF31s1CNbA==",
"version": "1.11.12",
"resolved": "https://registry.npmjs.org/msgpackr/-/msgpackr-1.11.12.tgz",
"integrity": "sha512-RBdJ1Un7yGlXWajrkxcSa93nvQ0w4zBf60c0yYv7YtBelP8H2FA7XsfBbMHtXKXUMUxH7zV3Zuozh+kUQWhHvg==",
"license": "MIT",
"optionalDependencies": {
"msgpackr-extract": "^3.0.4"
"msgpackr-extract": "^3.0.2"
}
},
"node_modules/msgpackr-extract": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/msgpackr-extract/-/msgpackr-extract-3.0.4.tgz",
"integrity": "sha512-4kmO/MdyUIkLIvTPr8VHLil4AtoKIoniWPIEk5+CDy0xnWC84azhSFmuJ7PxZdsYtiP5kEeQsORAVIeMgxT+Hw==",
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/msgpackr-extract/-/msgpackr-extract-3.0.3.tgz",
"integrity": "sha512-P0efT1C9jIdVRefqjzOQ9Xml57zpOXnIuS+csaB4MdZbTdmGDLo8XhzBG1N7aO11gKDDkJvBLULeFTo46wwreA==",
"hasInstallScript": true,
"license": "MIT",
"optional": true,
@@ -242,12 +238,12 @@
"download-msgpackr-prebuilds": "bin/download-prebuilds.js"
},
"optionalDependencies": {
"@msgpackr-extract/msgpackr-extract-darwin-arm64": "3.0.4",
"@msgpackr-extract/msgpackr-extract-darwin-x64": "3.0.4",
"@msgpackr-extract/msgpackr-extract-linux-arm": "3.0.4",
"@msgpackr-extract/msgpackr-extract-linux-arm64": "3.0.4",
"@msgpackr-extract/msgpackr-extract-linux-x64": "3.0.4",
"@msgpackr-extract/msgpackr-extract-win32-x64": "3.0.4"
"@msgpackr-extract/msgpackr-extract-darwin-arm64": "3.0.3",
"@msgpackr-extract/msgpackr-extract-darwin-x64": "3.0.3",
"@msgpackr-extract/msgpackr-extract-linux-arm": "3.0.3",
"@msgpackr-extract/msgpackr-extract-linux-arm64": "3.0.3",
"@msgpackr-extract/msgpackr-extract-linux-x64": "3.0.3",
"@msgpackr-extract/msgpackr-extract-win32-x64": "3.0.3"
}
},
"node_modules/multipasta": {
@@ -327,9 +323,9 @@
}
},
"node_modules/uuid": {
"version": "14.0.1",
"resolved": "https://registry.npmjs.org/uuid/-/uuid-14.0.1.tgz",
"integrity": "sha512-6ZxzVpzDXDa3bJWaHilVayA+BH/1zmxCJoVgvmqJnid/gPoKHxUrS/aC/T6LGQtNHT+XHG9fXPJB4d+IrU30Ew==",
"version": "13.0.1",
"resolved": "https://registry.npmjs.org/uuid/-/uuid-13.0.1.tgz",
"integrity": "sha512-9ezox2roIft6ExBVTVqibSd5dc5/47Sw/uY6b4SjQUT2TzQ0tltNquWA46y4xPQmdZYqvnio22SgWd41M86+jw==",
"funding": [
"https://github.com/sponsors/broofa",
"https://github.com/sponsors/ctavan"
@@ -355,9 +351,9 @@
}
},
"node_modules/yaml": {
"version": "2.9.0",
"resolved": "https://registry.npmjs.org/yaml/-/yaml-2.9.0.tgz",
"integrity": "sha512-2AvhNX3mb8zd6Zy7INTtSpl1F15HW6Wnqj0srWlkKLcpYl/gMIMJiyuGq2KeI2YFxUPjdlB+3Lc10seMLtL4cA==",
"version": "2.8.4",
"resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.4.tgz",
"integrity": "sha512-ml/JPOj9fOQK8RNnWojA67GbZ0ApXAUlN2UQclwv2eVgTgn7O9gg9o7paZWKMp4g0H3nTLtS9LVzhkpOFIKzog==",
"license": "ISC",
"bin": {
"yaml": "bin.mjs"
-2
View File
@@ -57,9 +57,7 @@ The 14 deep-dive guides under `docs/` (`guide_architecture.md`, `guide_ai_client
- `set_file_slice` IS valid for multi-line content. The agent must verify the exact byte offsets with `get_file_slice` first, copy the line text character-for-character (including whitespace and EOL), and check whether the edit changes a public contract (function signature, yield shape, return type) that other code depends on. See `conductor/edit_workflow.md` for the full contract.
- Do not use `git restore` while a user is mid-conversation without first confirming the desired state
- HARD BAN: `git restore`, `git checkout -- <file>`, `git reset` are FORBIDDEN without explicit user permission in the same message. They destroyed user in-progress src/* edits twice in one session (2026-06-07). If you think you need one, ASK FIRST.
- HARD BAN: `git stash*` (any form: `git stash`, `git stash pop`, `git stash apply`, `git stash drop`, `git stash clear`) is FORBIDDEN. Stashing inverts the safety net of the working tree: a `git add .` then `git stash` then "fresh start" pattern is exactly how Tier 2 corrupted files in the 2026-06-27 `cruft_elimination_20260627` track. The user explicitly stated "I hate when people fuck with my commits" — stashing throws away the user's in-progress edits silently. If you think you need a stash, you don't — use a NEW BRANCH or a WORKTREE instead. Tier 2 sandbox enforces this via `conductor/tier2/opencode.json.fragment` bash deny rules.
- **HARD BAN: Day estimates in track artifacts (Tier 1).** Do NOT include day / hour / minute estimates in spec.md, plan.md, metadata.json, or any other track artifact. Day estimates are inaccurate noise; Tier 2 capacity is bounded by attention, not time. Measure effort by **scope** (N files, M sites, N tasks). The user / Tier 2 agent decides the actual pacing. See `conductor/workflow.md` §"Tier 1 Track Initialization Rules" for the full rule, replacement patterns, and rationale. (Added 2026-06-16 per user feedback: "Day estimates are inaccurate. Tier-2s can only do so much in a single track and there is no way in hell its going to be 'DAYS'.")
- **HARD BAN: Opaque types in non-boundary code (added 2026-06-25).** LLMs default to `dict[str, Any]`, `Any`, `Optional[T]`, `hasattr()` polymorphism, and `.get('field', default)` because that's idiomatic Python training data. **All of these are BANNED in non-boundary code.** Use typed `@dataclass(frozen=True, slots=True)` with explicit fields; use `Result[T]` + `NIL_T` sentinels instead of `Optional[T]`; use direct attribute access instead of `.get()`. The ONLY place `dict[str, Any]` is allowed is the literal wire boundary (TOML/JSON parse functions); 2-3 functions per file. See `conductor/product-guidelines.md` "Core Value", `conductor/code_styleguides/data_oriented_design.md` §8.5 (The Python Type Promotion Mandate), `conductor/code_styleguides/python.md` §17 (LLM Default Anti-Patterns), and `conductor/code_styleguides/type_aliases.md` for the canonical mandates. User direction 2026-06-25: "I want the closest thing to c11/odin/jai in a scripting language... metadata should not be a dict[str, any]."
## File Size and Naming Convention (HARD RULE — added 2026-06-11)
@@ -1,99 +0,0 @@
{
"video": "C:\\projects\\manual_slop\\conductor\\tracks\\video_analysis_brain_counterintuitive_20260621\\artifacts\\video.mp4",
"threshold": 0.05,
"total_extracted": 121,
"kept": 91,
"files": [
"frame_00001.jpg",
"frame_00002.jpg",
"frame_00003.jpg",
"frame_00004.jpg",
"frame_00005.jpg",
"frame_00006.jpg",
"frame_00007.jpg",
"frame_00008.jpg",
"frame_00009.jpg",
"frame_00010.jpg",
"frame_00011.jpg",
"frame_00012.jpg",
"frame_00013.jpg",
"frame_00015.jpg",
"frame_00016.jpg",
"frame_00017.jpg",
"frame_00018.jpg",
"frame_00019.jpg",
"frame_00020.jpg",
"frame_00021.jpg",
"frame_00022.jpg",
"frame_00023.jpg",
"frame_00024.jpg",
"frame_00025.jpg",
"frame_00026.jpg",
"frame_00027.jpg",
"frame_00028.jpg",
"frame_00029.jpg",
"frame_00030.jpg",
"frame_00031.jpg",
"frame_00032.jpg",
"frame_00034.jpg",
"frame_00035.jpg",
"frame_00036.jpg",
"frame_00037.jpg",
"frame_00038.jpg",
"frame_00039.jpg",
"frame_00041.jpg",
"frame_00043.jpg",
"frame_00044.jpg",
"frame_00045.jpg",
"frame_00046.jpg",
"frame_00047.jpg",
"frame_00048.jpg",
"frame_00049.jpg",
"frame_00050.jpg",
"frame_00051.jpg",
"frame_00052.jpg",
"frame_00053.jpg",
"frame_00054.jpg",
"frame_00055.jpg",
"frame_00059.jpg",
"frame_00063.jpg",
"frame_00070.jpg",
"frame_00073.jpg",
"frame_00080.jpg",
"frame_00082.jpg",
"frame_00083.jpg",
"frame_00084.jpg",
"frame_00085.jpg",
"frame_00086.jpg",
"frame_00087.jpg",
"frame_00088.jpg",
"frame_00089.jpg",
"frame_00090.jpg",
"frame_00091.jpg",
"frame_00092.jpg",
"frame_00093.jpg",
"frame_00094.jpg",
"frame_00095.jpg",
"frame_00096.jpg",
"frame_00097.jpg",
"frame_00098.jpg",
"frame_00099.jpg",
"frame_00100.jpg",
"frame_00101.jpg",
"frame_00102.jpg",
"frame_00103.jpg",
"frame_00104.jpg",
"frame_00106.jpg",
"frame_00107.jpg",
"frame_00108.jpg",
"frame_00109.jpg",
"frame_00110.jpg",
"frame_00111.jpg",
"frame_00112.jpg",
"frame_00113.jpg",
"frame_00114.jpg",
"frame_00115.jpg",
"frame_00117.jpg",
"frame_00119.jpg"
]
}
Binary file not shown.

Before

Width:  |  Height:  |  Size: 191 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 212 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 196 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 200 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 213 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 186 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 263 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 238 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 253 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 287 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 292 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.3 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 399 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 161 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 154 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 227 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 96 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 52 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 297 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 172 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 272 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 305 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 126 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 150 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 239 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 156 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 131 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 138 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 948 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 582 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 926 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 612 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 363 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 88 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 868 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.7 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.1 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 544 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 526 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 438 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 378 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 388 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 418 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 457 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 476 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 481 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 481 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 500 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 505 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 514 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 551 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 547 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 587 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 606 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 649 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 651 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 376 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 378 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 373 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 465 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 759 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 529 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 215 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 253 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 304 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 416 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 569 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 337 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 772 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 152 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 943 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 246 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 280 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 323 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 248 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 382 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 305 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.0 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 199 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 207 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 78 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 75 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 109 KiB

Some files were not shown because too many files have changed in this diff Show More