AI_STARTS_HERE

AI STARTS HERE – engineering-platform#

Verpflichtender Einstieg#

1. Lies die Root-README.
2. Lies 00-overview/README.md.
3. Lies Engineering Platform Scope.
4. Lies Engineering Platform Contract.
5. Lies bei Build- oder Pipeline-Arbeiten Build Architecture und Pipeline Architecture.
6. Prüfe den Architecture Contract und den ausdrücklich beauftragten Scope.
7. Folge danach der nummerierten Verzeichnisreihenfolge und den Referenzen des betroffenen ⌘PlateausEin Plateau ist ein zeitlich eingeordneter, freigegebener Reife- oder Materialisierungsstand..

Entscheidungsregeln#

• Erfinde keine Architektur aus vorhandener Implementierung.
• Definiere Enterprise- oder Solution-Semantik nicht erneut.
• Dokumentiere Widersprüche als ⌘FindingTechnical documentation artifact. oder ADR-Vorschlag.
• Ändere keine Fakten, IDs oder Architekturentscheidungen eigenmächtig.
• Beende einen Sprint mit Navigation, Traceability, Validation, Verification und installierbarem Delta.

Plateau-Einstiege#

EP-000 – Workbench & Knowledge Foundation#

1. 00-overview/EP-000-workbench-knowledge-foundation.md
2. 20-frontend/EP-000-frontend-module-contract.md
3. 96-documentation/MVP-001-legacy-knowledge-seed.md

EP-001A – Domain Model#

• 00-overview/EP-001A-domain-model.md
• die darin referenzierten kanonischen Domain-Model-Dokumente der Solution Architecture.

EP-001B – Persistence#

• 60-persistence/EP-001B-persistence-boundary.md
• 60-persistence/migrations/0001_mvp_core.sql
• solution-architecture/70-data/EP-001B-persistence-model.md

EP-001C / EP-001D – Backend#

1. 10-backend/EP-001C-go-domain-repository.md
2. 10-backend/EP-001D-application-rest.md
3. 00-overview/EP-001A-domain-model.md
4. 60-persistence/EP-001B-persistence-boundary.md

EP-002 / EP-002.2 – Workbench#

• 00-overview/EP-002-platform-shell.md
• 20-frontend/EP-002-platform-composition.md
• 20-frontend/EP-002-2-manifest-driven-contribution-framework.md
• 20-frontend/EP-002-2C-workbench-observability-and-trace-logging.md

Querschnittsnachweise#

• 96-documentation/artifact-manifests.md
• 96-documentation/human-readable-code-contracts.md
• 96-documentation/EP-001-verification-coverage.md
• 00-overview/TRACEABILITY.md

Workspace-&-Roundtrip-Einstieg#

1. 00-overview/roundtrip/WORKSPACE_CONTRACT.md
2. 00-overview/roundtrip/ROUNDTRIP_ARCHITECTURE.md
3. 00-overview/roundtrip/CHANGED_ONLY_ROUNDTRIP_CONTRACT.md
4. 00-overview/roundtrip/EXCHANGE_MANIFEST_CONTRACT.md
5. 95-tests/ROUNDTRIP_TEST_CONTRACT.md

Import-/Export-&-Packaging-Einstieg#

1. 00-overview/roundtrip/PACKAGE_CLASSIFICATION_CONTRACT.md
2. 00-overview/roundtrip/IMPORT_CONTRACT.md
3. 00-overview/roundtrip/EXPORT_CONTRACT.md
4. 00-overview/roundtrip/PACKAGING_ARCHITECTURE.md
5. 90-installer/INSTALLATION_BOUNDARY.md
6. 95-tests/IMPORT_EXPORT_PACKAGING_TEST_CONTRACT.md

Validation & Verification#

• Validation Contract
• Verification Contract
• Validation and Verification Architecture
• Validation Verification Test Contract
• EP-005 Report

Automation & Orchestration#

1. Automation Architecture
2. Orchestration Contract
3. Execution Run Contract
4. Trigger Contract
5. Retry and Idempotency Contract
6. Automation Approval Boundary
7. Automation Orchestration Test Contract
8. EP-006 Report

Engineering Runtime#

1. Engineering Runtime Architecture
2. Engineering Runtime Contract
3. Runtime Lifecycle Contract
4. Runtime Configuration Contract
5. Engineering Runtime Model
6. Engineering Runtime Test Contract
7. EP-007 Report

Engineering Governance#

1. Development Guidelines
2. Engineering Change Workflow
3. Artifact Import and Delete Rules
4. Engineering Governance Architecture
5. Governance Contract
6. Policy and Guideline Hierarchy
7. Change Authority Contract
8. Decision Governance Contract
9. Engineering Governance
10. Engineering Governance Test Contract
11. EP-008 Report

Engineering Requirements#

1. Requirements Architecture
2. Requirement Contract
3. Requirement Lifecycle Contract
4. Acceptance Criteria Contract
5. Requirement Traceability Contract
6. Engineering Requirements
7. Engineering Requirements Test Contract
8. EP-009 Report

Repository-Klassifikation#

Dieses Repository ist ein Engineering Repository. Der AI-Einstieg ist Bestandteil des verbindlichen Root-Vertrags.

Vor jeder Änderung sind zu prüfen:

1. Identität, Version und repositoryClass in ◆manifest.json,
2. der Verantwortungsrahmen in README.md,
3. der beauftragte Scope,
4. der repositoryeigene Validierungseinstieg validation.md.

Responsibility Boundaries#

Vor Änderungen, die andere Repositorys berühren, zusätzlich lesen:

1. 00-overview/RESPONSIBILITY_BOUNDARIES.md
2. enterprise-architecture:00-overview/cross-repository-responsibility-model.md

Repositoryübergreifende Referenzvalidation#

Für Multi-Repository-Roundtrips zusätzlich lesen:

1. 00-overview/CROSS_REPOSITORY_REFERENCE_VALIDATION_INTEGRATION.md
2. 00-overview/RESPONSIBILITY_BOUNDARIES.md

Build Contract#

1. 00-overview/pipeline/BUILD_ARCHITECTURE.md
2. 00-overview/pipeline/BUILD_CONTRACT.md
3. 96-documentation/BUILD_CONTRACT_EVIDENCE.md

Deployment Contract#

1. 00-overview/DEPLOYMENT_ARCHITECTURE.md
2. 00-overview/DEPLOYMENT_CONTRACT.md
3. 96-documentation/DEPLOYMENT_CONTRACT_EVIDENCE.md

Workspace Contract Realization#

1. 00-overview/roundtrip/WORKSPACE_CONTRACT.md
2. 96-documentation/WORKSPACE_CONTRACT_EVIDENCE.md

KT-0016 Validation Contract#

Verbindliche Referenz: 96-documentation/VALIDATION_CONTRACT_EVIDENCE.md

KT-0017 Contract Coverage Review#

1. 96-documentation/CONTRACT_COVERAGE_GAP_REVIEW.md