dynamicalsystem.com / tinsnip
homelab infrastructure services
fork atom
tinsnip / ooda /
at main 1 folder 1 file
dynamicalsystem.com docs(ooda): Complete reorganization from docs/ooda to ooda/
6a732b71
2025-10-multi-service-architecture
README.md
README.md

OODA Loop Tracking#

This directory contains outcome-based OODA (Observe, Orient, Decide, Act) loop documentation.

Current Status: [~] ACT In Progress#

Active Outcomes#

2025-10-multi-service-architecture#

Status: [~] ACT Phase In Progress Start Date: 2025-10-18 Directory: 2025-10-multi-service-architecture/

Enable multiple catalog services to deploy to one machine with shared UID, central port allocation, and per-service .env files.

Progress:

  • OBSERVE Complete (2 audits)
  • ORIENT Complete (3 designs)
  • DECIDE Complete (5 decisions approved)
  • [~] ACT In Progress (0/5 branches merged)

Quick Links:

Structure#

ooda/
├── README.md                                    # This file
├── branch_implementation_plan.md                # Legacy: Original flat plan (deprecated)
└── 2025-10-multi-service-architecture/          # Outcome folder (date-prefixed)
    ├── README.md                                # Outcome status dashboard
    ├── decision.md                              # Architecture decisions
    ├── workflow.md                              # How to track progress
    ├── observe/                                 # OBSERVE phase documents
    │   ├── registry-audit.md
    │   └── env-location-audit.md
    ├── orient/                                  # ORIENT phase designs
    │   ├── machine-metadata.md
    │   ├── service-env.md
    │   └── port-allocation-algorithm.md
    └── act/                                     # ACT phase implementation
        ├── 01-registry-rename-smep/
        │   ├── plan.md                          # Implementation checklist
        │   └── BRANCH.md                        # Status tracking
        ├── 02-machine-metadata/
        ├── 03-port-allocation/
        ├── 04-service-env/
        └── 05-service-catalog/

Creating New OODA Outcomes#

When starting a new significant architectural change:

  1. Create date-prefixed outcome folder: YYYY-MM-outcome-name/
  2. Create phase subdirectories: observe/, orient/, act/
  3. Add outcome README.md with status dashboard
  4. Add decision.md for architecture decisions
  5. Track individual branches in act/NN-branch-name/ folders

Legacy Documents#