Decision
Toorow maintains a private working repository while exporting a strictly allow-listed projection to public repositories. This approach separates core shareable application code from private marketing, design, and product planning workspace assets.Public Application Projection
The shareable application projection includes only paths explicitly allowed indistribution/public-app.toml:
Private Workspace Projection
The following surfaces remain strictly private and are excluded from public application exports:Why an Allow-List Policy?
Deny-list policies risk exposing private files when new directories or temporary local databases are introduced. The allow-list model enforces a default-private security stance: any new path is private unless explicitly reviewed and added todistribution/public-app.toml.
Defense-in-depth deny rules further scrub environment files (.env), credentials, local SQLite/DuckDB databases, and scratch data from allowed directories before export.
Export & Release Workflow
- Execute
python scripts/export_public_app.py --listto inspect allowed export targets. - Export snapshot to an isolated build directory outside the repository.
- Run automated secret scanner (
ruff, secret-grep) over the exported tree. - Verify license inclusion prior to describing the repository as open-source.
- Human approval (Human Gate) is required before pushing public releases.
Next Steps & Cross-References
Security Constraints
Review pre-live security checklists and architectural invariants.
Self-Hosting Guide
Deploy your own instance of toorow.