master
66cb6c4b8a
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
- Introduced guild charters for Scanner Deno, PHP, Ruby, Native, WebService, Java, Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, UI, Zastava Observer, Zastava Webhook, Zastava Core, and Plugin Platform. - Each charter outlines the mission, scope, required reading, and working agreements for the respective guilds. - Created task boards for Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, and Zastava components to track progress and dependencies. - Ensured all documents emphasize determinism, offline readiness, security, and integration with shared Surface libraries.
Platform Architecture & Module Dossiers
Use this index to locate architecture narratives, boundaries, and implementation plans for every Stella Ops component.
Core Views
- ../high-level-architecture.md – 10-minute overview of the end-to-end flow.
- ../07_HIGH_LEVEL_ARCHITECTURE.md – exhaustive reference (data flows, trust boundaries, operational traits).
- ../40_ARCHITECTURE_OVERVIEW.md – design principles applied across modules.
- ../scanner-core-contracts.md – canonical DTOs shared by Scanner services and consumers.
- Legacy service dossier: ../11_AUTHORITY.md – Authority overview before module split.
- UI documentation set: ../../ui/ (navigation, policies, findings, runs, tours).
- Component map: component-map.md – quick descriptions of every
src/module and how they interact.
Module Catalogue
Each module directory bundles an ownership charter (AGENTS.md), current work (TASKS.md), architecture dossier, and implementation plan. Operations guides live under operations/ where applicable.
Tip: Every module directory also exposes
README.md,AGENTS.md, andTASKS.mdfor roles, current backlog, and ownership responsibilities.