Files
svrnty-vision/INDEX.md
T
2026-06-18 03:15:36 -04:00

32 lines
2.1 KiB
Markdown

# Svrnty Vision Index
Route: `svrnty-vision`.
Path: `/home/svrnty/workspaces/cortex-os/svrnty-vision`.
Category: child-local sovereign vision HTTP gateway and Visual Perception Package Candidate workspace.
Validator: `python3 tools/validate_svrnty_vision_child.py`.
## Read Order
1. `AGENTS.md` for route-local authority, forbidden effects, and validator rules.
2. `README.md` for gateway posture, operator/developer examples, and cleanup-route boundary.
3. `docs/LEGACY-INGEST.md` for legacy intention coverage and rejection gates.
4. `docs/VISION-PACKAGE-CANDIDATE.md`, `docs/VISUAL-EVIDENCE-CONTRACT.md`, and `docs/VISION-HOST-ADAPTER-CANDIDATES.md` for package-candidate work.
5. `candidate-manifests/` for tool grants and manifest contracts.
6. `WORKBOARD.yaml` for child-local work state.
## Local Authority
Svrnty Vision owns child-local VLM, FLUX, palette, and cutout gateway source; BTE-shaped HTTP route adapters; package-candidate docs; visual-evidence contracts; host-adapter candidates; tool-grant manifests; Docker package context; validators; fixtures; and proof packets.
Svrnty Vision is not Core authority, Seed installation authority, Runtime startup authority, Host Runtime authority, Docker lifecycle authority, Profile Exposure authority, provider admission authority, wildcard tool authority, product-readiness authority, release authority, or production authority.
## Legacy Relation
Older BTE-embedded vision, cloud-provider SDK, VLM, FLUX, palette, rembg, Visual Evidence, and package-candidate work is distilled into this standalone gateway only when current docs and validators admit the intention. Do not import provider credentials, backend state, runtime behavior, cloud-provider coupling, wildcard tool access, or implementation mass because it exists.
## Completion State
Stage: CLEAN.
Clean score: 100.
Current next pass: keep this route static unless a governed route authorizes Docker, FastAPI/Uvicorn, endpoint calls, Spark/ComfyUI/vLLM calls, provider calls, package installation, Profile Exposure, Seed installation, Runtime startup, or readiness claims.