Skip to content

About

MicroTodoSuite constitution, architecture decisions, delivery conventions, and rollout plans.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

MicroTodoSuite Documentation

This repository holds the governing documents of MicroTodoSuite: the constitution, the architecture and delivery decisions, and the plans for the full-platform rollout. GaCode Solutions designs, builds, and operates the platform for its client, Lexfield Legal. The repository contains no executable code.

Governing documents

Document Purpose
Constitution The non-negotiable principles, the operational baseline, and the amendment process.
Pull request and task tracking conventions The binding branch, commit, pull-request, language, and task-tracking rules. Constitution principle 13 makes them mandatory.
ADR-0001: Multicloud strategy Why AWS is the single primary platform and Azure an independent recovery domain.
Governance and IaC standards program The 2026 governance and infrastructure-as-code program and its recorded decisions.

Architecture and delivery

Document Purpose
Architecture The current platform architecture and the retired Azure Container Apps design.
Branching strategy The branching model used by every repository.
Agile methodology The Kanban method and the delivery board.
Evolution plan The consolidated plan for the migration from Azure Container Apps to AWS EKS, with the economical and full profiles.
Architecture review The 2026-08-09 review of the target architecture against the validated workspace state.

Full-platform rollout

Document Purpose
Rollout index The stages of the full-platform rollout, their owners, and their order.
Infrastructure execution plan The sequencing of the infrastructure lane.
Capacity, regions, and the account parameter The limits that let both profiles run at once in one account, and the region placement.
Economical safety boundary What protects the economical platform while the full profile is built.
Plan reconciliation The task registers reconciled against delivered reality.
Work allocation The remaining work distributed across the team lanes.

Contributing

Every change follows the pull request and task tracking conventions and the repository's pull-request template. Documents are written in English, in a professional register and in the third person, without emoji. A change to the constitution follows its amendment process.

About

MicroTodoSuite constitution, architecture decisions, delivery conventions, and rollout plans.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages