Skip to content

🧠 Compute Strategy: Adopted-Active Control Plane

This document defines which tasks in the inputs/** -> stack-tech-core/** -> bidirectional governance model run locally and which are enforced in GitHub Actions for atlantyqa-universe.

⚖️ Decision matrix

Task Resources Risk ⚙️ Local ☁️ GitHub Actions
🧪 Validate adoption request (repo-bootstrap) Low (CPU) High ✅ Primary ✅ Verification
🛡️ Verify migration to stack-tech-core/** Low (CPU) High ✅ Primary ✅ Gate
📚 Regenerate adopted-project living docs Low (CPU) Medium ✅ Primary ✅ Check
📘 Build MkDocs portal ES/EN Medium (CPU/RAM) Medium ✅ Primary ✅ CI
🧩 Create canonical adopted-active issues Low Medium ✅ Primary ⚠️ Issue-trigger only
🔐 main guards + collaborator approval gates Low Critical ⚠️ Local evidence ✅ Mandatory
⚖️ SL legal normalization step 1 Low High ✅ Primary ⚠️ Validation only

🧭 Operating rules

  • Local (work source): prepare changes, evidence packs, runbooks, and legal normalization artifacts.
  • GitHub Actions (enforcement source): main gates, contract checks, approval controls, and documentation consistency.
  • Never assume human decisions: every L0KY, Angel, or Bosco decision must be explicit in issue/PR evidence.

🔐 Security and traceability

  • Never push secrets, .env files, tokens, or sensitive industrial material.
  • Any move from inputs/** to stack-tech-core/** must be reflected in bidirectional governance catalog entries.
  • No merge to main without passing required control and approval workflows under .github/contracts/.