Status: scaffolded Publication state: public scaffold Release state: not released
application-development-systems is a Phase 7 public scaffold for public-safe application architecture and AI-assisted software delivery discipline.
This repo is not a live app, active customer project, deployed software surface, released software package, production endpoint catalog, private source mirror, or production secret store.
| Field | Value |
|---|---|
| Status | scaffolded |
| Publication state | public scaffold |
| Release state | not released |
| Public GitHub repo | published scaffold |
| First artifact | app-architecture/public-safe-nextjs-architecture.md completed as scaffolded synthetic artifact |
| Published artifact | scaffolded |
| Released artifact | private/not-public or not released |
| Profile routing | planned |
| Proof-stack routing | planned |
The scaffold covers synthetic Next.js, TypeScript, Tailwind, shadcn/ui, review workflow, validation, deployment assumption, and ownership-boundary documentation.
- Next.js and TypeScript as public-safe architecture references.
- Tailwind and shadcn/ui as generic component-pattern references.
- Vercel, Supabase, and Stripe only as generic boundary notes where needed.
- Codex-style AI-assisted delivery as a reviewed workflow pattern, not as autonomous production delivery.
All examples must separate personal proof, generic app architecture, product-boundary notes, client-owned app boundaries, and private source boundaries. No customer data, credentials, production endpoints, or private source may appear.
AI-assisted delivery examples must show bounded planning, patching, review, validation, and human approval. They must not include internal prompts, private logs, live tool tokens, or autonomous production claims.
Review workflows cover synthetic pull-request checks, boundary review, claim review, and validation gates.
Deployment notes are assumptions only. They do not prove deployment, uptime, released software, active customers, or production readiness.
Run scripts/validate-public-boundary.sh, the plan-listed boundary/status rg scan, git diff --check, git status --short, and git remote -v.
This repo contains public-safe application-development architecture and delivery discipline only. It must not contain live apps, active customer claims, deployed software claims, released software claims, production endpoints, credentials, secrets, customer data, private source, unreleased product internals, private design systems, private logs, private prompts, live tool tokens, client-owned app confusion, production secrets, or internal company product names.
Profile routing and proof-stack routing are planned only. Any links from Franzabner or franzabner-proof-stack require separate reviewed patches.
First artifact completed as scaffolded: app-architecture/public-safe-nextjs-architecture.md covers synthetic app context, Next.js / TypeScript / Tailwind / shadcn/ui structure, ownership boundary, AI-assisted delivery workflow, validation plan, Mermaid diagram, proof limits, and public/private/sealed checklist.