Policy gates before remote execution
ACCEPTEDAgents get a constrained interface; operators keep credentials and approval.
Remote actions cross a meaningful trust boundary. Explicit policy and approval keep capability separate from authority.
Engineering decisions
The constraints are part of the system.
Short records of choices that shape how I build trustworthy software and agent infrastructure.
Durable files over hidden application state
ACCEPTEDPortable data remains inspectable after the surrounding tool changes.
Plain, versionable records make state easier to audit, migrate, repair, and own without depending on one interface.
Unrestricted agent access to infrastructure
REJECTEDConvenience is not worth an invisible production trust boundary.
Broad credentials turn an agent mistake into an infrastructure incident. Narrow tools and scoped permissions make failures containable.