Inventory
Agent Action BOM
The practical inventory for actor, owner, repo, workflow, credential, reachable action, target, approval rule, and proof.
Independent research, field notes, and frameworks on AI-assisted software delivery.
CAISI / Frameworks
Field notes explain what is changing. Frameworks turn that pressure into reusable operating models: what to inventory, what to approve, what evidence to keep, and how to decide whether an AI-assisted workflow is ready for more autonomy.
Core frameworks
Inventory
The practical inventory for actor, owner, repo, workflow, credential, reachable action, target, approval rule, and proof.
Control model
A model for classifying actions as allowed, approval-required, or blocked at the execution boundary.
Evidence
A proof-packet model for actor, owner, credential, action, target, approval, validation, outcome, and re-review triggers.
Delivery controls
A concrete control path for PRs, workflow files, CI/CD, credentials, tool calls, approval, and proof trails.
Operating models
Field guide
The highest-level CAISI guide to control, execution boundaries, proof, and governed adoption.
Stack model
An OSI-inspired model for separating compute, models, context, orchestration, tools, authority, control, and domain action.
Maturity
A staged way to move from individual AI assistance to reliable, inspectable, and governed AI-assisted delivery.
Evaluation
Scenario, efficacy, proof, and pilot language for comparing control quality without relying on demo claims.
Operating guides
Map action authority, credentials, MCP/tool reach, CI/CD actions, approvals, and proof.
Evaluate tool reach, invocation context, credential context, approval triggers, and proof fields.
Reduce standing-token and inherited-identity risk across agents, CI/CD, tools, and release paths.
Plain-language definitions for write paths, proof packets, approval mediation, and execution boundaries.