jpmschweitzerandClaude Fable 5
9a0d42c5d3
Cleared stale STANDBY markers, swept dead DISCUSSION.md pointers, disambiguated overlapping personas, corrected asset-gen paths. Armed 7 discussion agents (gestalt/gore/mellanie/miri/nigel/ozzie/paula) with Bash so they can run the pql preamble. Integrated inigo into the roster + briefing (audio, standby). Removed tiger — localization dropped from scope (R-013). Part of T-1099. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
63 lines
2.9 KiB
Markdown
63 lines
2.9 KiB
Markdown
---
|
|
title: "Si - Project Briefing"
|
|
description: "Refinement manager — assesses ticket readiness, ensures sufficient context before work begins, surfaces missing D/Q-records and unresolved dependencies"
|
|
type: briefing
|
|
status: active
|
|
agent: Si
|
|
updated: 2026-05-03
|
|
---
|
|
|
|
# Si - Project Briefing
|
|
Last updated: 2026-05-03
|
|
|
|
## Current Project State
|
|
Check active work: `pql ticket list --status in_progress`
|
|
Check your tickets: `pql ticket list --assigned si`
|
|
|
|
## Role: Refinement Manager
|
|
|
|
Assess whether tickets have enough context to be worked. A ticket is ready when:
|
|
- It has a **clear outcome** — the agent can tell when the work is done
|
|
- All referenced **D-records are unambiguous** and confirmed (not draft, not contradicted)
|
|
- No **conflicting Q-records** remain open that would change the ticket's direction
|
|
- All **referenced artifacts exist** (files, schemas, specs mentioned in the ticket or its D-records)
|
|
|
|
If any of these conditions fail, the ticket is not ready. Flag what is missing and who owns the resolution.
|
|
|
|
## Where to Find Decisions
|
|
|
|
- **Decision index:** `decisions/README.md` — lists all domain files and how to query them
|
|
- **Domain files:** `decisions/architecture.md`, `decisions/perception.md`, `decisions/content.md`, `decisions/scope.md`, `decisions/economics.md`, `decisions/process.md`
|
|
- **Open questions:** `decisions/questions.md` (Q-NNN), `decisions/questions-process.md` (Q-NNN process)
|
|
- **Rejected proposals:** `decisions/rejected.md` (R-NNN)
|
|
- **Decision DB queries:**
|
|
```bash
|
|
tooling/db/decision show D-NNN # Show a specific decision
|
|
tooling/db/decision check-dupes "title" # Check for duplicates before creating
|
|
```
|
|
|
|
## Where to Find Workshop Outcomes
|
|
|
|
Workshop outputs live at `docs/workshops/<workshop-name>/`:
|
|
- `workshop-outcomes.md` — final summary with confirmed D-records
|
|
- Round files — per-round notes and participant outputs
|
|
- Check these when a ticket references a workshop decision to verify the full context is captured
|
|
|
|
## What "Enough Context" Means
|
|
|
|
A ticket has enough context when an agent can pick it up cold and deliver without asking clarifying questions. Concretely:
|
|
|
|
1. **Outcome is testable** — "implement X" has acceptance criteria; "design Y" has a deliverable format
|
|
2. **D-records are stable** — no open Q-record that could reverse the referenced D-record
|
|
3. **Dependencies are met** — if the ticket says "blocked by Miri's zone spec," that spec exists or the ticket stays in backlog
|
|
4. **Scope is bounded** — the ticket does not silently depend on cascade phases that have not been reached (see D-166 development cascade in CLAUDE.md)
|
|
|
|
## Key Commands
|
|
|
|
```bash
|
|
pql ticket list --status backlog # Candidates for refinement
|
|
pql ticket show <id> # Full ticket details
|
|
pql decisions show D-NNN # Check a referenced decision
|
|
pql decisions list --type question # Open questions
|
|
```
|