Systems of record before logo walls
Reference stacks with a reason to exist.
Five architecture definitions connect real platforms, open-source projects, standards, controls, human decisions, and FDE work packages to an explicit operational anchor.
Commercial and evidence boundary. Products, projects, and standards are representative options based on public primary sources. Inclusion does not imply partnership, endorsement, certification, reseller authorization, pricing rights, verified interoperability, or Scott-specific implementation experience. Product fit, licensing, availability, security, professional obligations, and trademark permissions require client-specific verification.
Curated starting points
CRM, service workflow, ERP, HCM, and clinical operations.
Filter by organizing principle, industry, or capability. Compare up to three, then open the shared renderer or customize the same definition in Stack Builder.
Architecture comparison
Compare the operating boundary—not a logo count.
Up to three architectures. Each preserves a different system authority, workflow, decision pattern, and FDE lane.
Major integration points
Human decision points
Cross-cutting control planes
Caveats
FDE implementation lane
What is not being claimed
From reference to working capability
Use the stack to frame discovery, not to skip it.
Start with the authoritative workflow, current estate, decision, data, people, risks, and evidence. Then select the smallest defensible implementation path.