arckit-cli 6.1.1__py3-none-any.whl

arckit_cli-6.1.1.data/data/share/arckit/scripts/autoresearch/fixtures/000-global/ARC-000-PRIN-v1.0.md

@@ -0,0 +1,120 @@
+# Architecture Principles
+
+| Field | Value |
+|-------|-------|
+| Document ID | ARC-000-PRIN-v1.0 |
+| Document Type | Architecture Principles |
+| Project | Global |
+| Classification | OFFICIAL |
+| Status | DRAFT |
+| Version | 1.0 |
+| Created Date | 2026-03-20 |
+| Last Modified | 2026-03-20 |
+| Review Cycle | Quarterly |
+| Next Review Date | 2026-06-20 |
+| Owner | Lead Architect |
+| Reviewed By | [PENDING] |
+| Approved By | [PENDING] |
+| Distribution | Architecture Team |
+
+## Revision History
+
+| Version | Date | Author | Changes | Approved By | Approval Date |
+|---------|------|--------|---------|-------------|---------------|
+| 1.0 | 2026-03-20 | Lead Architect | Initial draft | [PENDING] | [PENDING] |
+
+---
+
+## Principles
+
+### P-001: Cloud-First
+
+**Category:** Technology
+
+**Rationale:** Managed cloud services reduce operational overhead, improve elasticity, and accelerate delivery compared to on-premise infrastructure. HM Government's cloud-first policy mandates evaluation of cloud options before considering alternatives.
+
+**Implications:**
+
+- All new services must be designed for cloud deployment (AWS, Azure, or GCP via G-Cloud).
+- On-premise hosting requires a formal exception approved by the Lead Architect.
+- Infrastructure must be provisioned as code (Terraform or equivalent).
+
+---
+
+### P-002: API-First Design
+
+**Category:** Application
+
+**Rationale:** Exposing all capabilities via well-defined APIs enables reuse, supports future channel expansion (mobile, voice, third-party integration), and decouples front-end from back-end evolution.
+
+**Implications:**
+
+- No capability may be delivered solely through a user interface; a corresponding API must exist.
+- APIs must be documented to OpenAPI 3.x standard before go-live.
+- Internal APIs are subject to the same standards as public-facing APIs.
+
+---
+
+### P-003: Security by Design
+
+**Category:** Technology
+
+**Rationale:** Security controls embedded from inception are cheaper and more effective than those retrofitted post-build. NCSC Cyber Assessment Framework (CAF) alignment is required for public-facing government services.
+
+**Implications:**
+
+- Threat modelling (STRIDE or equivalent) must be completed at architecture design stage.
+- Zero-trust network model: no implicit trust based on network location.
+- All data in transit must use TLS 1.2 or above; data at rest must be encrypted.
+- Penetration testing required before go-live and annually thereafter.
+
+---
+
+### P-004: Data Minimisation
+
+**Category:** Data
+
+**Rationale:** Collecting only the data necessary for the stated purpose reduces GDPR compliance risk, limits the impact of a data breach, and builds citizen trust.
+
+**Implications:**
+
+- Data requirements must justify each data element with a lawful basis before collection.
+- Personal data retention periods must be defined and enforced by automated deletion.
+- Data sharing with third parties requires a Data Sharing Agreement and DPIA.
+
+---
+
+### P-005: Open Standards
+
+**Category:** Technology
+
+**Rationale:** Open formats and protocols prevent vendor lock-in, promote interoperability with other government systems, and align with the Government's Open Standards Principles.
+
+**Implications:**
+
+- Prefer open standards (JSON, REST, OAuth 2.0, OpenID Connect) over proprietary equivalents.
+- Proprietary formats require an approved exception with documented exit strategy.
+- All APIs must support standard authentication protocols (OAuth 2.0 / OIDC).
+
+---
+
+### P-006: User-Centred Design
+
+**Category:** Business
+
+**Rationale:** Services designed around real user needs — evidenced by research — achieve higher adoption, reduce support costs, and meet GDS Service Standard assessment requirements.
+
+**Implications:**
+
+- User research must be conducted before, during, and after service delivery.
+- All public-facing touchpoints must meet WCAG 2.2 AA accessibility standard.
+- GOV.UK Design System components must be used for citizen-facing interfaces.
+- Services must pass a GDS service assessment at Alpha and Beta stages.
+
+---
+
+**Generated by:** ArcKit `/arckit:principles` command
+**Generated on:** 2026-03-20
+**ArcKit Version:** 4.4.0
+**Project:** Global (Project 000)
+**Model:** claude-sonnet-4-5-20250929

arckit_cli-6.1.1.data/data/share/arckit/scripts/autoresearch/fixtures/001-test-project/ARC-001-STKE-v1.0.md

@@ -0,0 +1,100 @@
+# Stakeholder Analysis
+
+| Field | Value |
+|-------|-------|
+| Document ID | ARC-001-STKE-v1.0 |
+| Document Type | Stakeholder Analysis |
+| Project | Digital Appointment Booking Service (Project 001) |
+| Classification | OFFICIAL |
+| Status | DRAFT |
+| Version | 1.0 |
+| Created Date | 2026-03-20 |
+| Last Modified | 2026-03-20 |
+| Review Cycle | Monthly |
+| Next Review Date | 2026-04-20 |
+| Owner | Lead Architect |
+| Reviewed By | [PENDING] |
+| Approved By | [PENDING] |
+| Distribution | Project Team |
+
+## Revision History
+
+| Version | Date | Author | Changes | Approved By | Approval Date |
+|---------|------|--------|---------|-------------|---------------|
+| 1.0 | 2026-03-20 | Lead Architect | Initial draft | [PENDING] | [PENDING] |
+
+---
+
+## Stakeholders
+
+### Power/Interest Grid
+
+```text
+High Power │ Service Owner (SRO)   │ Head of Digital
+           │ [Manage Closely]      │ [Keep Satisfied]
+           ├───────────────────────┼──────────────────────────────
+Low Power  │                       │ Lead Architect
+           │ [Monitor]             │ Call Centre Ops Manager
+           │                       │ [Keep Informed]
+           └───────────────────────┴──────────────────────────────
+                  Low Interest              High Interest
+```
+
+### STK-001: Service Owner (SRO)
+
+**Power:** High | **Interest:** High | **Grid Position:** Manage Closely
+
+**Goals:** Reduce call centre operating costs by 40%; achieve service go-live within 12 months; demonstrate measurable citizen satisfaction improvement.
+
+**Influence Strategy:** Engage in monthly steering group. Provide concise RAG status reports. Escalate blockers immediately. Align architecture decisions to cost and timeline goals.
+
+---
+
+### STK-002: Head of Digital
+
+**Power:** High | **Interest:** Medium | **Grid Position:** Keep Satisfied
+
+**Goals:** Achieve GDS service assessment pass at Alpha and Beta; deliver reusable platform components (authentication, notifications) for adoption by other departmental services.
+
+**Influence Strategy:** Share architecture decisions that affect platform reuse. Involve in key design reviews. Provide GDS compliance evidence proactively.
+
+---
+
+### STK-003: Lead Architect
+
+**Power:** Medium | **Interest:** High | **Grid Position:** Keep Informed
+
+**Goals:** Deliver a cloud-native, maintainable, and secure architecture aligned to P-001–P-006 principles; establish patterns reusable across future projects.
+
+**Influence Strategy:** Primary author of all architecture artefacts. Chair architecture review board. Own ADR log.
+
+---
+
+### STK-004: Call Centre Operations Manager
+
+**Power:** Low | **Interest:** High | **Grid Position:** Keep Informed
+
+**Goals:** Ensure smooth transition from telephony to digital channel; secure budget and time for staff retraining; maintain service continuity during rollout.
+
+**Influence Strategy:** Include in user research sessions. Provide monthly progress updates. Involve in acceptance testing to build confidence.
+
+---
+
+## RACI Matrix
+
+| Deliverable | Service Owner | Head of Digital | Lead Architect | Call Centre Ops |
+|-------------|---------------|-----------------|----------------|-----------------|
+| Requirements | A | C | R | C |
+| Architecture | I | C | R/A | I |
+| Testing | A | I | C | C |
+| Deployment | A | I | R | C |
+
+**R** = Responsible, **A** = Accountable, **C** = Consulted, **I** = Informed
+
+---
+
+**Generated by:** ArcKit `/arckit:stakeholders` command
+**Generated on:** 2026-03-20
+**ArcKit Version:** 4.4.0
+**Project:** Digital Appointment Booking Service (Project 001)
+**Model:** claude-sonnet-4-5-20250929

arckit_cli-6.1.1.data/data/share/arckit/scripts/autoresearch/fixtures/001-test-project/README.md

@@ -0,0 +1,15 @@
+# Digital Appointment Booking Service
+
+**Project ID:** 001
+**Created:** 2026-03-20
+
+A UK government digital service enabling citizens to book, reschedule, and cancel
+appointments online. Part of a department's digital transformation programme to
+reduce call centre volume by 60% and improve citizen satisfaction.
+
+## Key Stakeholders
+
+- Service Owner (SRO)
+- Head of Digital
+- Lead Architect
+- Call Centre Operations Manager