This repository is a curated blueprint for building and operating a venture from formation through a secure, multi-device workspace and production runtime. It turns early research into a practical set of decisions, requirements, and operating standards.
- Read Desired e2e Use Cases, User Journeys, and Technical Specification for the target operating model and acceptance criteria.
- Use Business Structure and Capital Planning to prepare questions for qualified legal and tax advisers.
- Use Workspace Architecture and Operating Model to select controls and tools appropriate to organizational maturity.
- Execute Implementation Roadmap in stages; do not adopt enterprise tooling before its operating owner and evidence requirements exist.
- Follow GitHub Delivery Standard for contribution, review, release, and repository-security practices.
| Location | Purpose |
|---|---|
docs/ |
Shareable, curated project documentation |
.archive/business-structuring/ |
Git-ignored original source conversations and long-form research; retained locally for traceability |
AGENTS.md |
Contribution and editorial guidance |
Use managed control planes and open standards where they reduce operational risk; keep developer work local and reproducible. Separate personal from organizational identity, everyday from privileged access, and development from production. A workstation is an execution environment, not the authoritative home for source, secrets, policies, accounts, or recovery material.
This is a planning resource, not legal, tax, investment, or security certification advice. Validate jurisdiction, contracts, regulatory obligations, and product configurations with qualified professionals before execution.
Contributions use short-lived branches, pull requests, conventional commits, and protected main. Releases are tag-based and use semantic versioning. See CONTRIBUTING.md, SECURITY.md, and the delivery standard.