1. Patterns are building blocks, not a program of everything
The architecture guide names six patterns a company can build. They are organizational capabilities, not a portfolio piece. Pick the one that matches the decision you wrote down. A program that starts all six starts none of them.
2. Documents, search, and meetings
Document intelligence turns paper and files into structured records. Route among a parser, OCR, a layout model, and a multimodal model. Validate the schema, the confidence, the region on the page the value came from, and the exceptions a person must see. A pretty extraction with no exception path will silently accept the bad page.
Enterprise search answers from material the user is allowed to see. That means ingestion that respects structure, hybrid retrieval, a reranker, access control, an answer grounded in citations, a willingness to abstain, and an eval. A chat that cannot say “I do not have this” will invent a source.
Conversation intelligence works from meetings and calls. Transcription, who spoke, the decision and the action, a timestamp you can open, consent, retention, and a way to correct the record. A summary with no timestamp is a rumor with punctuation.
3. A private model, an agent, or the outcome first
A sovereign engine is the comparison, not the assumption that private is better. Put the private serving next to a managed baseline on quality, latency, capacity, privacy, availability, and the full bill. Keep the winner for that workload. Re-compare when the workload changes.
A multi-step agent is justified when the path adapts and a fixed script cannot. It needs explicit state, typed tools, least privilege, a trace, a budget, an approval boundary, a way to repeat a step safely, and a way to roll back. If the path is a fixed rule, write the rule. Deterministic software remains the default for calculations, permissions, and irreversible controls.
Work backwards. Start from the user, the decision, the outcome, the process, the data, the controls, and the eval. Select the technology last. This is the pattern to use when a vendor demo arrived before the problem statement. It is also the pattern the other five should be able to survive.
4. One platform question underneath
Architecture knowledge in a large company is scattered across documents, spreadsheets, catalogs, SQL, pipeline definitions, diagrams, tickets, and meetings. A serious search or agent will eventually ask “what breaks if this field changes?” That question needs lineage and an owner, not a larger prompt. The change-impact classes are ordinary: source, schema, transformation, pipeline, quality, the report a person uses, the security or regulatory exposure, and the operational cutover. You do not need all of those on day one. You need to know which one your first workflow actually hits.
5. What to pick
Circle one pattern. Write the user, the decision, and the unacceptable failure. If a second pattern seems required, it is a later phase, not a second team starting tomorrow.
The order of the work is a reference picture and a first roadmap.