Project Phase: Phase 1 Complete (Infrastructure Sealed)
This project implements a secure, scalable email system functionality for Assistants Company, starting with AWS Infrastructure.
- Phase 0: Foundation (Identity, Audit, Verification).
- Phase 1: Infrastructure (AWS Organization, VPC, EKS, RDS, Redis, S3, CI/CD, Observability).
- Phase 2: App Core (Backend API).
Important
GOVERNANCE ENFORCEMENT: This repository follows a strict "Governance First" approach. All code must adhere to the Canonical Repository Tree defined in the Implementation Plan.
FAIL-CLOSED: The system is designed to fail-closed on any uncertainty or violation of guards.
The repository is organized into the following canonical roots:
foundation/: The ONLY allowed shared dependency surface. Contains Contracts, Runtime Primitives, and Guards.chapters/: Self-contained, deployable modules (12 Chapters). No cross-chapter imports allowed.spine/: Python package roots ensuring clean import paths.apps/: Frontend applications (Next.js/React).ops/: CI/CD pipelines, security scans, and operational scripts.
- Inventory First: Before creating any file, check
foundation/docs/INVENTORY_LIST.mdto prevent duplication. - Ultra Micro Phases (UMPs): Development proceeds in atomic units (UMPs).
- Each UMP is its own
feat/branch. - Each UMP produces 5 mandatory files:
CONTEXT,PROMPT,SPEC,CODE,TEST_VISUAL.
- Each UMP is its own
- Visual Verification: No UMP is sealed until visually verified (Screenshot or Terminal Output).
- Sealing: Once verified, UMPs are sealed (hashed) and cannot be edited.
- Python 3.10+
- Node.js 18+
- Docker (for local services)
This project adheres to strict governance protocols:
- Diamond Brick Protocol: Branch -> Code -> Test -> Visual -> Seal.
- Inventory: All files tracked in
inventory.md. - Verification: Visual proofs required for all chapters.
Built with Governance by NerdyFox Co.