Guides

Each workflow below maps to one or two free-tier tool calls. None of them needs a Strata19 account or a model key unless noted.

Understand an unfamiliar repository

Call strata19.initialize_project with the repository's absolute path, then ask for the repository reality — the inline card that surfaces unreachable-file candidates, silent-swallows, placeholders, and duplicate functions within seconds of binding. For a specific symbol or change, follow with strata19.get_implementation_context or strata19.compute_change_impact (find-references, callers, callees, via the tree-sitter symbol graph) rather than reading files speculatively. Treat the analyzed-coverage note on the response as part of the answer, not boilerplate — a scan that hit an unsupported file type or an unresolved import says so rather than silently skipping it.

Capture durable work

When a change, bug, decision, or specification delta comes up in conversation, capture it immediately with strata19.manage_work_item rather than letting it live only in the transcript. The draft pre-fills from the local code index — touched files, symbols, blast radius, related findings — and is never rejected for being incomplete; it refines one question at a time until you confirm the objective and acceptance criteria.

Resume after interruption

Before or after a meaningful change, call strata19.create_or_get_checkpoint to save the current graph state. In the next conversation — a new session, possibly a different model — read the relevant work item and checkpoint instead of asking the agent to reconstruct prior context from a transcript it may not have.

Verify a change

Run strata19.verify_implementation as the local verification gate, and read the evidence and caveats it returns, not just the pass/fail line. Compare the current checkpoint against the one from before the change to see which findings are new, gone, or still present — see Core Concepts for what "gone" does and does not prove. Reopen the work item if the comparison doesn't actually support calling it done.

Generate a Specbook with BYOK

Configure a model provider key (OPENAI_API_KEY or STRATA19_MODEL_KEY, optionally STRATA19_SPECBOOK_BUDGET_USD to cap estimated spend), then run strata19.spec_generate. Review the generated sections before treating them as accepted intent — every section is written as a proposal (origin: generated), never as verified fact. Run strata19.spec_sync after later code changes to keep it current without losing anything you've hand-edited, and strata19.spec_view to read the same content through the product, engineering, quality, security, or code lens.

Stay inside the local Stop gate

If your host supports Claude Code-style hooks and you've trusted them (/hooks, once, in Codex — see Reference), a Stop hook re-runs the same four detectors scoped to the files you touched this session before letting the conversation end. The default mode (ask) presents any high/critical finding and a proposed fix and waits for your go-ahead before changing anything; it never edits silently.