Macroscope Template

Macroscope Template

Owner: Client Intake Manager (Camille) Produced for: IT Architecture Team + Enterprise Architect (Elena) Purpose: High-level vision/context that shapes design decisions When to use: See decision rule in production line Stage 1 (intake)

Client & Engagement

Client Name: [name] Engagement Type: [digital talent type — e.g., enterprise architect agent, customer support bot, etc.] Client Contact: [name + role] Date Created: [YYYY-MM-DD]

Vision

What does the client want to achieve with this digital talent? Describe the intended outcome and impact in their business context.

[Client's vision in 2-3 sentences]

Operating Context

Deployment Environment

  • Where: [internal network, cloud SaaS, embedded in existing system, external/client-facing, etc.]
  • Users: [who uses this talent — internal staff, external customers, both]
  • Access model: [internal tool, client-facing, embedded in workflow, etc.]

Integrations Required

  • [List systems/APIs this talent must connect to]
  • [Data sources or platforms it accesses]
  • [Authentication/authorization requirements]

Scale & Constraints

  • User count: [current + growth target]
  • Compliance/regulatory: [ISO 27001, SOC 2, HIPAA, GDPR, industry-specific standards, etc. — or "None identified"]
  • Performance requirements: [response time, availability, throughput, etc. — or "Standard/no special requirements"]
  • Data sensitivity: [public, internal, confidential, regulated — impacts architecture]
  • Geographic constraints: [data residency, availability zones, etc. — or "None"]

Success Metrics

Client Success (How STM measures this talent's value)

  • [Metric 1: what they want to achieve or improve]
  • [Metric 2]
  • [Metric 3]

Factory Success (How we measure delivery quality)

  • Deployed and operational by [TARGET DATE]
  • Client satisfaction score ≥ [target]/10
  • [Any quality/reliability target specific to this engagement]
  • [Maintenance/support overhead target — or "TBD"]

Methodology & Frameworks

Framework Library: Check production-lines/digital-talent/frameworks/ for available framework packages. If the client's required framework is not in the library, flag for Francois (Framework Specialist) to build the package before proceeding.

Recommended Framework

Primary: [framework name — TOGAF, ISO/IEC/IEEE 42010, Zachman, ArchiMate, CMMI, etc.] Rationale: [Why this framework aligns with the client's context] Library Package: [path to framework package in library, or "Not yet available — Francois to build"]

Alternative Frameworks (for consideration)

  • [Framework 2 — when it might apply instead]
  • [Framework 3 — when it might apply instead]

Decision: [Which framework will be used and why. Reference the framework library package selected from production-lines/digital-talent/frameworks/. Framework Specialist (Francois) input recommended.]

Key Assumptions

List any assumptions made during intake that affect architecture decisions:

  • [Assumption 1]
  • [Assumption 2]
  • [Assumption 3]

Open Questions (Follow-up with Client)

Questions to clarify before design begins:

  • [Question 1 — person to answer, deadline if any]
  • [Question 2]
  • [Question 3]

Next Steps

Immediate

  1. Elena (Enterprise Architect) → designs the digital talent architecture using this macroscope
  2. IT Architecture Team → validates Elena's design against macroscope intent
  3. Approved macroscope → stored at production-lines/orders/{order-slug}/macroscope.md

Downstream

  1. Elena → produces architecture documentation (system design, boundaries, integration specs)
  2. Pablo (Production Line Architect) → builds the agent based on validated architecture
  3. Camille/Dana → brief client on approved design before build starts

Notes

[Space for Camille's notes, context, or relationship details that shape how to engage with this client.]

This macroscope is the north star. Every architecture and build decision downstream should trace back to it.