The map comes before the build
A company request normally arrives as an object: a dashboard, an agent, a chatbot, an automation. The build starts beneath the object, with the recurring work, record, decision, delay, and exception the object is meant to change.
The map establishes the current workflow and the first measurable production boundary. Without it, the quote prices uncertainty and the build discovers its purpose after engineering has started.
The company context is part of the infrastructure
Generic AI can access general knowledge. A working company system needs approved sources, identity, terminology, rules, examples, source priority, and a way to handle conflicts.
That context must be versioned and inspectable. Otherwise the system becomes another person whose reasoning nobody can audit.
Connections need readback
Authentication is not the same as a working integration. A connection is production-ready only after a real scoped event has been read, transformed, written where permitted, and read back from the receiving system.
Rate limits, retries, duplicates, expired credentials, and partial failures are part of the install, not support surprises.
Human approval is a system component
Review mode is not a temporary embarrassment. It is how the team sees real behavior before authority is granted.
Authority should be narrow: one action class, one channel, explicit limits, visible escalation, and an audit trail.
Acceptance replaces the reveal
The acceptance test is agreed before work begins. It defines the cases, expected outputs, controls, failure behavior, and readback that count as done.
The system launches when it passes the written test, not when the demo looks convincing.