docs: sync constitution with installed presets#30
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR updates TinyPl0’s governance/documentation surfaces to reflect newly installed Spec-Kit presets, adding a general iSAQB/arc42 architecture governance layer and propagating it into templates and agent guidance, alongside refreshed project statistics and IDE version metadata.
Changes:
- Adds general architecture governance guidance (iSAQB/arc42; ADRs and
docs/architecture/evidence expectations) and propagates it across agent guidance files. - Syncs Spec-Kit spec/plan/tasks templates and command templates to explicitly schedule/validate architecture evidence work when architecture is in scope.
- Updates
docs/project-statistics.mdand bumpsPl0.Idepackage/version metadata.
Reviewed changes
Copilot reviewed 15 out of 15 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| src/Pl0.Ide/Pl0.Ide.csproj | Bumps IDE version metadata to the new commit/branch target. |
| .specify/memory/constitution.md | Adds Principle XX in the Spec-Kit constitution mirror and updates mirror metadata. |
| .specify/templates/spec-template.md | Extends constitution requirements to include architecture applicability/evidence expectations. |
| .specify/templates/plan-template.md | Adds planning gates for architecture evidence scope and ADR/risk tracking. |
| .specify/templates/tasks-template.md | Adds foundational tasks for architecture evidence, ADRs, and scenario/risk validation. |
| .specify/templates/commands/constitution.md | Updates constitution command guidance to include syncing command templates too. |
| .specify/templates/commands/checklist.md | Ensures checklists include architecture evidence completeness checks. |
| .specify/templates/commands/spec.md | Updates spec command guidance to require architecture applicability/evidence impacts. |
| .specify/templates/commands/plan.md | Updates plan command guidance to include architecture evidence scope as a gate. |
| .specify/templates/commands/tasks.md | Updates tasks command guidance to schedule architecture evidence tasks when relevant. |
| docs/project-statistics.md | Refreshes ledger totals, adds a new ledger entry, and updates summary diagrams/figures. |
| AGENTS.md | Adds the general architecture governance and agentic architecture workflow sections. |
| CLAUDE.md | Adds the general architecture governance and agentic architecture workflow sections. |
| GEMINI.md | Adds the general architecture governance and agentic architecture workflow sections. |
| .github/copilot-instructions.md | Adds the general architecture governance and agentic architecture workflow sections. |
| - Konservative Handarbeits-Basis fuer Code und Dokumentation: | ||
| - 162 Zeilen netto gesamt | ||
| - 2.0 Arbeitstage fuer einen erfahrenen Entwickler | ||
| - 15.8 Stunden auf TVoeD-Basis (`2.0 * 7.8`) |
Comment on lines
+303
to
+310
| - Verbindliche Regeln und Evidenzpfade: siehe `constitution.md`, Prinzip XX. | ||
| - Architekturarbeit SOLL iSAQB/CPSA-F-Methodik und leichtgewichtige arc42-kompatible Dokumentation verwenden. | ||
| - Architekturrelevante Entscheidungen MÜSSEN als ADRs dokumentiert werden; allgemeine ADRs standardmäßig in `docs/architecture/adr/`. | ||
| - Systemkontext, Building Blocks, Runtime-Sichten, Deployment-Zwänge, Qualitäts-Szenarien sowie Architektur-Risiken oder akzeptierte Trade-offs MÜSSEN dokumentiert werden, wenn sie das Design materiell beeinflussen. | ||
| - Allgemeine Architektur-Evidenz liegt standardmäßig unter `docs/architecture/`; Sicherheitsarchitektur verbleibt unter `docs/security/`. | ||
| - Änderungen an dieser Regel erfordern ein gemeinsames Update in `constitution.md`, `.specify/memory/constitution.md`, `AGENTS.md`, `CLAUDE.md`, `GEMINI.md` und `.github/copilot-instructions.md`. | ||
|
|
||
| *Software architecture MUST be treated as an explicit design artefact whenever changes affect structure, interfaces, quality attributes, runtime behavior, deployment, or technical debt. Authoritative rules: `constitution.md`, Principle XX. Architecture work SHOULD use iSAQB/CPSA-F discipline and lightweight arc42-compatible documentation. Architecturally significant decisions MUST be recorded as ADRs, defaulting to `docs/architecture/adr/`. Context, building blocks, runtime/deployment views, quality scenarios, and architecture risks or trade-offs MUST be documented when they materially affect the design. General architecture evidence defaults to `docs/architecture/`; security architecture remains under `docs/security/`. Changes require a joint update across `constitution.md`, `.specify/memory/constitution.md`, and all four agent guidance files.* |
Comment on lines
+290
to
+297
| - Verbindliche Regeln und Evidenzpfade: siehe `constitution.md`, Prinzip XX. | ||
| - Architekturarbeit SOLL iSAQB/CPSA-F-Methodik und leichtgewichtige arc42-kompatible Dokumentation verwenden. | ||
| - Architekturrelevante Entscheidungen MÜSSEN als ADRs dokumentiert werden; allgemeine ADRs standardmäßig in `docs/architecture/adr/`. | ||
| - Systemkontext, Building Blocks, Runtime-Sichten, Deployment-Zwänge, Qualitäts-Szenarien sowie Architektur-Risiken oder akzeptierte Trade-offs MÜSSEN dokumentiert werden, wenn sie das Design materiell beeinflussen. | ||
| - Allgemeine Architektur-Evidenz liegt standardmäßig unter `docs/architecture/`; Sicherheitsarchitektur verbleibt unter `docs/security/`. | ||
| - Änderungen an dieser Regel erfordern ein gemeinsames Update in `constitution.md`, `.specify/memory/constitution.md`, `AGENTS.md`, `CLAUDE.md`, `GEMINI.md` und `.github/copilot-instructions.md`. | ||
|
|
||
| *Software architecture MUST be treated as an explicit design artefact whenever changes affect structure, interfaces, quality attributes, runtime behavior, deployment, or technical debt. Authoritative rules: `constitution.md`, Principle XX. Architecture work SHOULD use iSAQB/CPSA-F discipline and lightweight arc42-compatible documentation. Architecturally significant decisions MUST be recorded as ADRs, defaulting to `docs/architecture/adr/`. Context, building blocks, runtime/deployment views, quality scenarios, and architecture risks or trade-offs MUST be documented when they materially affect the design. General architecture evidence defaults to `docs/architecture/`; security architecture remains under `docs/security/`. Changes require a joint update across `constitution.md`, `.specify/memory/constitution.md`, and all four agent guidance files.* |
Comment on lines
+162
to
+169
| - Verbindliche Regeln und Evidenzpfade: siehe `constitution.md`, Prinzip XX. | ||
| - Architekturarbeit SOLL iSAQB/CPSA-F-Methodik und leichtgewichtige arc42-kompatible Dokumentation verwenden. | ||
| - Architekturrelevante Entscheidungen MÜSSEN als ADRs dokumentiert werden; allgemeine ADRs standardmäßig in `docs/architecture/adr/`. | ||
| - Systemkontext, Building Blocks, Runtime-Sichten, Deployment-Zwänge, Qualitäts-Szenarien sowie Architektur-Risiken oder akzeptierte Trade-offs MÜSSEN dokumentiert werden, wenn sie das Design materiell beeinflussen. | ||
| - Allgemeine Architektur-Evidenz liegt standardmäßig unter `docs/architecture/`; Sicherheitsarchitektur verbleibt unter `docs/security/`. | ||
| - Änderungen an dieser Regel erfordern ein gemeinsames Update in `constitution.md`, `.specify/memory/constitution.md`, `AGENTS.md`, `CLAUDE.md`, `GEMINI.md` und `.github/copilot-instructions.md`. | ||
|
|
||
| *Software architecture MUST be treated as an explicit design artefact whenever changes affect structure, interfaces, quality attributes, runtime behavior, deployment, or technical debt. Authoritative rules: `constitution.md`, Principle XX. Architecture work SHOULD use iSAQB/CPSA-F discipline and lightweight arc42-compatible documentation. Architecturally significant decisions MUST be recorded as ADRs, defaulting to `docs/architecture/adr/`. Context, building blocks, runtime/deployment views, quality scenarios, and architecture risks or trade-offs MUST be documented when they materially affect the design. General architecture evidence defaults to `docs/architecture/`; security architecture remains under `docs/security/`. Changes require a joint update across `constitution.md`, `.specify/memory/constitution.md`, and all four agent guidance files.* |
Comment on lines
+384
to
+391
| - Verbindliche Regeln und Evidenzpfade: siehe `constitution.md`, Prinzip XX. | ||
| - Architekturarbeit SOLL iSAQB/CPSA-F-Methodik und leichtgewichtige arc42-kompatible Dokumentation verwenden. | ||
| - Architekturrelevante Entscheidungen MÜSSEN als ADRs dokumentiert werden; allgemeine ADRs standardmäßig in `docs/architecture/adr/`. | ||
| - Systemkontext, Building Blocks, Runtime-Sichten, Deployment-Zwänge, Qualitäts-Szenarien sowie Architektur-Risiken oder akzeptierte Trade-offs MÜSSEN dokumentiert werden, wenn sie das Design materiell beeinflussen. | ||
| - Allgemeine Architektur-Evidenz liegt standardmäßig unter `docs/architecture/`; Sicherheitsarchitektur verbleibt unter `docs/security/`. | ||
| - Änderungen an dieser Regel erfordern ein gemeinsames Update in `constitution.md`, `.specify/memory/constitution.md`, `AGENTS.md`, `CLAUDE.md`, `GEMINI.md` und `.github/copilot-instructions.md`. | ||
|
|
||
| *Software architecture MUST be treated as an explicit design artefact whenever changes affect structure, interfaces, quality attributes, runtime behavior, deployment, or technical debt. Authoritative rules: `constitution.md`, Principle XX. Architecture work SHOULD use iSAQB/CPSA-F discipline and lightweight arc42-compatible documentation. Architecturally significant decisions MUST be recorded as ADRs, defaulting to `docs/architecture/adr/`. Context, building blocks, runtime/deployment views, quality scenarios, and architecture risks or trade-offs MUST be documented when they materially affect the design. General architecture evidence defaults to `docs/architecture/`; security architecture remains under `docs/security/`. Changes require a joint update across `constitution.md`, `.specify/memory/constitution.md`, and all four agent guidance files.* |
Comment on lines
1
to
8
| <!-- | ||
| Sync Impact Report | ||
| Version change: 1.11.0 -> 1.12.0 | ||
| Version change: 1.12.0 -> 1.13.0 | ||
| Modified principles: | ||
| - None (purely additive) | ||
| Added sections: | ||
| - None | ||
| - XX. General Architecture Governance (iSAQB / arc42) | ||
| Removed sections: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Testing