> ## Documentation Index > Fetch the complete documentation index at: https://panaptico.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Blueprints > The versioned, structured container for an implementation A blueprint is the top-level container for an implementation in Panaptico. It holds every surface — the checklist, the ontology, the diagrams, the stakeholder map, the audit trail, the evidence, the health history — in a single versioned, auditable workspace. ## What a blueprint contains A blueprint is not a document. It is a live project workspace with the following surfaces: ### Project overview The intelligence dashboard showing health scores, risk posture, velocity, and an overall A–F grade across scored domains (execution, risk, evidence, scope integrity, ownership, operational readiness, freshness). ### Systems ontology The discovered map of your environment — systems, resources, relationships, and integrations. Each mapping has a state: confirmed, inferred, or flagged. ### Implementation checklist The sequenced rollout plan. Phased tasks with: * Dependencies (task X blocks task Y) * Acceptance criteria * Evidence requirements (files, screenshots, test results, links) * Approval gates with named approvers * Owners and assignees * Execution results and AI-assisted diagnostics * Risk and blocker tracking ### Architecture diagrams Interactive node-link graphs showing task dependencies, critical path, and status. Available as dependency diagram, Gantt chart, or Kanban board. ### Process flows Cross-system workflows discovered from your environment — showing actors, systems, durations, variants, and bottlenecks. ### Stakeholder map and RACI Organizational roles and relationships with: * Interactive stakeholder diagram * RACI matrix (responsible, accountable, consulted, informed) per task * Ownership matrix with required functions and assignment status * Unresolved decisions with escalation paths ### Goals and success metrics Measurable outcomes tied to the implementation, each with up to three success signals (metric + target value). ### Post-implementation plan What happens after go-live: * Support model and SLA structure * Monitoring and alerting setup * Feature adoption tracking * Stakeholder communications * Continuous improvement tracking ### File vault All generated and uploaded artifacts — configs, exports, evidence files, logs, manifests — stored with the blueprint and linked to specific tasks. ### Audit trail Every action timestamped and attributed: blueprint changes, AI tool usage, artifact generation, approvals, task state changes, exports, settings changes, and version activity. ## Blueprint lifecycle | Stage | What happens | | -------------- | ----------------------------------------------------------------------------------------------------------- | | **Generation** | Systems Architect discovers your environment and produces the initial implementation structure | | **Execution** | Teams work through the checklist — completing tasks, attaching evidence, routing approvals, resolving risks | | **Monitoring** | Health snapshots track progress, drift, and risk posture over time | | **Go-live** | The implementation transitions to post-implementation — the same graph becomes the operational baseline | | **Operations** | Health monitoring, drift detection, adoption tracking, and continuous improvement continue indefinitely | ## Versioning and reuse Blueprints are versioned. Every change to the implementation state is recorded in the audit trail. Blueprints can be used as templates for repeatable implementations — the structure carries forward while the project-specific context (evidence, approvals, stakeholder assignments) resets. ## Next steps How tasks get executed with evidence and approvals Create your first blueprint