ja
6dbe59e117
- Delete deprecated CLAUDE.md - Create root-level AGENTS.md for AI assistant guidance - Create SDD constitution in .specify/memory/constitution.md - Align documentation with PARA structure (docs/product/project-brief.md, docs/tech/stack.md, docs/plans/) - Add standardized YAML frontmatter to all documentation files - Update README.md with saTway branding and structure
35 lines
1.4 KiB
Markdown
35 lines
1.4 KiB
Markdown
---
|
|
description: >-
|
|
The mw-pfeddersheim-workstation constitution defining the non-negotiable
|
|
principles for development and infrastructure management.
|
|
tags:
|
|
- sdd
|
|
- constitution
|
|
- principles
|
|
- workstation
|
|
last_updated: '2026-03-09'
|
|
---
|
|
|
|
# mw-pfeddersheim-workstation Constitution
|
|
|
|
## Article I: Intent is Truth
|
|
The source of truth for all system changes is the intent documented in the `specs/` and `docs/` directories. No configuration change should exist without a documented rationale.
|
|
|
|
## Article II: Baby Steps™ Imperative
|
|
All modifications MUST follow the Baby Steps™ methodology:
|
|
1. Atomic changes only.
|
|
2. Focus on process over outcome.
|
|
3. One task at a time.
|
|
4. Complete and verify before moving to the next.
|
|
5. Mandatory incremental verification.
|
|
6. Document progress in `docs/learnings/`.
|
|
|
|
## Article III: Configuration-as-Code
|
|
All system configurations that can be automated MUST be managed via Ansible roles. Manual changes are allowed only when automation is impossible or prohibitively complex, and they MUST be documented in `docs/tech/manual-overrides.md`.
|
|
|
|
## Article IV: Zero-Trust Security
|
|
No raw secrets, tokens, or private keys shall ever be committed to the repository. Use `ansible-vault` or system-level environment variables.
|
|
|
|
## Article V: Performance & Reliability
|
|
All infrastructure changes should prioritize system stability and performance. Maintenance scripts MUST be robust and follow the satware AG bash script standards.
|