Documentation
Architecture concepts
Define a task, its permitted inputs and actions, and the result a user can inspect. This is conceptual documentation, not an API reference.
Responsibility
A bounded unit of work with an outcome, allowed context, permitted actions and an accountable reviewer.
Context boundary
The place source data is processed, any bounded information that may leave, and the policy governing it.
Authority and oversight
The difference between reading, drafting, changing and approving consequential work.
Execution and recovery
Model, tool and device choices plus the handling of errors, interruptions and incomplete work.
Responsibility
Define a final state a user can inspect.
“Prepare a reviewable update from these approved records” is a usable responsibility. “Be autonomous” is not: it leaves the work, boundary and accountability undefined.
Context boundary
Follow what data is used and where.
Execution and recovery
Design for the real device and workflow.
Validate latency, memory, model quality, thermal behavior, connectivity changes, cancellation, interruption recovery and partial results in the target environment.
The presence of a local runtime does not by itself prove a workflow is private, reliable or ready for production. Verify the complete data path and failure behavior.