Files
CASAN/infra/local-prod/README.md
T
thanhnvandClaude Opus 4.8 36a4812ef3 refactor(structure): promote app to repo root + remove redundant workspace cruft
Standard production layout: the OKR app (was nested under AINative_OKR_CASAN5/) is now
the repository root. No more wrapper directory.

- Promote AINative_OKR_CASAN5/* -> repo root (backend/ frontend/ packages/ apps/
  .specify/ docs/ infra/ nginx/ scripts/ + configs). Merge tool dirs: .gitea (kept the
  active deploy ci.yml, added harness-ci.yml + runbooks), .claude (agents/commands +
  launch.json), .github moved up.
- Remove redundant: 00_SUBMISSION_PACKAGE, scattered root notes (FPT_CASAN_Full.md,
  tu-tuong-casan.md, casan-tu-sinh..., casan_harness_assessment.md, source-review...,
  README_CASAN5_REFINED.md), casan-next-plans/ and optimize-docs/ (competition/planning
  artifacts — roadmap + design history preserved in git log / commit messages).
- Update all references to the old layout:
  - .gitea/workflows/{ci,harness-ci}.yml, .github/workflows/{ci,deploy}.yml:
    working-directory .; drop AINative_OKR_CASAN5/ prefix; .specify/{tests,scripts}
    -> packages/casan-harness/... (.specify/logs state kept)
  - .claude/launch.json, .gitea/*-runbook.md: path prefixes
  - CLAUDE.md, README.md: docs/input -> apps/okr/domain/input
  - policy-bundle.yaml: 8 policy paths -> packages/casan-harness/...; manifest re-signed
- secrets-scan.sh: fixture excludes -> new package/domain paths.

Full gate from the new root: PASS=64 FAIL=0 SKIP=3.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-08 13:26:36 +09:00

30 lines
1.3 KiB
Markdown

# CASAN Local Production-Like Infra Lab
This Docker Compose stack emulates the external infrastructure needed to move
CASAN Tier 2 from "needs infra" to locally testable production-like controls.
## Services
| Service | Local URL | Purpose |
|---|---|---|
| Vault dev | `http://127.0.0.1:18200` | KMS Transit signing/rotation/non-exportable keys |
| Mock IdP/OIDC | `http://127.0.0.1:18081` | RS256 JWT + JWKS for approval identity |
| MinIO | `http://127.0.0.1:19090` | S3-compatible WORM/Object Lock emulation |
| MinIO Console | `http://127.0.0.1:19091` | Object store admin UI |
| Alert webhook | `http://127.0.0.1:19092` | Slack/PagerDuty-style webhook emulator |
| Billing API mock | `http://127.0.0.1:19093/usage` | Provider usage API emulator |
| Dashboard via nginx | `http://127.0.0.1:18080` | Dashboard behind basic auth (`casan` / `casan`) |
## Commands
```bash
bash .specify/scripts/bash/infra-lab.sh start
bash .specify/scripts/bash/infra-lab.sh verify
bash .specify/scripts/bash/infra-lab.sh env
bash .specify/scripts/bash/infra-lab.sh stop
```
This is a lab, not a compliance claim. AWS S3 Object Lock, real enterprise IdP,
CloudHSM, PagerDuty/Slack, and OpenAI/Anthropic billing APIs still need real
managed services and credentials before claiming production Strong readiness.