Files
mw-pfeddersheim-workstation/docs/plans/2026-02-27-initial-setup-plan.md
ja 6dbe59e117 docs: align with satware AG best practices
- 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
2026-03-09 11:02:17 +01:00

2.1 KiB

description, tags, last_updated
description tags last_updated
Historical implementation plan for the initial baseline of the mw-pfeddersheim-workstation infrastructure.
plan
history
baseline
2026-02-27

Initial Implementation Plan - 2026-02-27

Establish a stable infrastructure baseline for the mw-pfeddersheim-workstation by committing existing files, implementing missing Ansible tasks, and cleaning up legacy tool remnants.

This plan focuses on transition the repository from an uncommitted state to a managed baseline. It addresses the user's specific request to remove VS Code remnants and local AI tools while setting up a robust maintenance routine through Ansible and shell scripts. The goal is to ensure Michael Wegener's workstation is reproducible and follows the defined saTway standards.

Files & Components

Updates existing Ansible roles and creates a new learning log for context restoration.

New files:

  • docs/learnings/2026-02-27-initial-setup.md: Documentation of the initial repository state and first baseline.
  • ansible/roles/maintenance/tasks/main.yml: Implementation of system cleanup and maintenance tasks.
  • ansible/roles/dev-tools/tasks/main.yml: Implementation of development tool management (installation of core tools, removal of legacy ones).

Existing files to be modified:

  • scripts/maintenance.sh: Enhanced to handle the --check flag and integrate better with Ansible-driven cleanup.

Configuration updates:

  • .gitignore: Ensure all relevant system and Ansible files are correctly tracked or ignored.

Implementation Order

The sequence is designed to establish a git baseline before making system-level changes.

  1. Create initial learning log for documentation.
  2. Perform initial git commit of all untracked infrastructure files.
  3. Create feat/initial-baseline branch for subsequent changes.
  4. Implement ansible/roles/maintenance/tasks/main.yml including VS Code and AI tool cleanup.
  5. Implement ansible/roles/dev-tools/tasks/main.yml for core tool validation.
  6. Update scripts/maintenance.sh to support --check mode.
  7. Execute Ansible playbook in check mode, then apply.