Kits

Agent release domain overlay composed over the agent-operation base kit. The base supplies the operating layer (Actor, WorkItem, ReviewRequest, Decision, Risk, OpenQuestion, StateNote plus their ownership, review-gate, work-axis, and governed-judgment relationships, queries, guards, and checks). This overlay adds the agent release DOMAIN: agent systems, their versions, eval suites, and receipted eval runs — and one hard gate: an AgentVersion cannot be promoted to live without an accepted, passing, certifying EvalRun.

4 types · 6 queries · 1 guards

$ init --kit agent-operation --kit agent-release

agent-release →

Case-law monitoring domain overlay composed over the agent-operation base. The corpus layer is real public law: opinions, courts, judges, statutes, and the citation graph (CourtListener-sourced, digest-pinned seed; live refresh via a utility fetch). The firm layer is the practice: clients, matters, arguments, filings, deadlines, case outcomes. Governed edges carry the legal judgments an attorney reviews: holdings, statutory interpretations, citation treatment, argument support/risk, matter impact, filing obligations.

12 types · 21 queries · 20 workflows

$ init --kit agent-operation --kit case-law-monitoring

case-law-monitoring →

Local of the KEV reference world model for internal vulnerability triage. The reference layer (Vendor, Product, Vulnerability) comes from public feeds and is read-only. This overlay adds internal assets, services, controls, and the accepted judgment relationships that link public vulnerabilities to internal operational impact.

7 types · 7 queries · 5 workflows

$ state create-overlay --state-ref kev-reference --kit kev-triage

kev-triage →

Project/product domain overlay composed over the agent-operation base kit. The base supplies the operating layer (Actor, SubjectRef, WorkItem, ReviewRequest, Decision, Risk, OpenQuestion, StateNote plus their ownership, review-gate, work-axis, governed-judgment, and subject-ref relationships, queries, guards, and checks). This overlay adds the project/product DOMAIN: roadmap items, release lines, and milestones as typed entities, product areas and capabilities as lightweight tag-role classification, and the domain-internal plus seam relationships that connect operation entities to domain structure. It composes the project/product domain on top of the agent-operation base. Markdown docs, plans, chats, review reports, and transcripts remain source evidence for proposals; they are not modeled as entities here.

5 types · 11 queries

$ init --kit agent-operation --kit project-domain

project-domain →

Supply-chain incident blast-radius domain overlay composed over the agent-operation base. Deterministic base world of suppliers, components, assemblies (recursive BOM), products, and shipments — the launch seed is a real open-hardware BOM with fictional suppliers in real geographies. Incidents arrive as entities and cascade through three staged governed workflows: incident -> supplier -> component/direct assembly. Product and shipment risk are derived context surfaces over accepted upstream impacts, BOM structure, buffers, and shipment state — never direct incident-product edges. Governed edges are rule-centric (bucket signatures carry the cascade rule, not the incident), so trust accumulates on rules across incidents. Operating-layer seams: work items address incidents; risks attach to suppliers through the governed path.

9 types · 30 queries · 13 workflows

$ init --kit agent-operation --kit supply-chain-blast-radius

supply-chain-blast-radius →

Published vulnerability reference graph built from public data: CISA KEV, NVD CVE/CPE configurations, and EPSS scores. Products use CPE-based identifiers. Vulnerability-to-product edges carry affected version ranges from NVD CPE match data.

kev-reference →