feat(docs): Add comprehensive documentation for Vexer, Vulnerability Explorer, and Zastava modules
- Introduced AGENTS.md, README.md, TASKS.md, and implementation_plan.md for Vexer, detailing mission, responsibilities, key components, and operational notes. - Established similar documentation structure for Vulnerability Explorer and Zastava modules, including their respective workflows, integrations, and observability notes. - Created risk scoring profiles documentation outlining the core workflow, factor model, governance, and deliverables. - Ensured all modules adhere to the Aggregation-Only Contract and maintain determinism and provenance in outputs.
This commit is contained in:
		
							
								
								
									
										40
									
								
								docs/modules/authority/README.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										40
									
								
								docs/modules/authority/README.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,40 @@ | ||||
| # StellaOps Authority | ||||
|  | ||||
| Authority is the platform OIDC/OAuth2 control plane that mints short-lived, sender-constrained operational tokens (OpToks) for every StellaOps service and tool. | ||||
|  | ||||
| ## Responsibilities | ||||
| - Expose device-code, auth-code, and client-credential flows with DPoP or mTLS binding. | ||||
| - Manage signing keys, JWKS rotation, and PoE integration for plan enforcement. | ||||
| - Emit structured audit events and enforce tenant-aware scope policies. | ||||
| - Provide plugin surface for custom identity providers and credential validators. | ||||
|  | ||||
| ## Key components | ||||
| - `StellaOps.Authority` web host. | ||||
| - `StellaOps.Authority.Plugin.*` extensions for secret stores, identity bridges, and OpTok validation. | ||||
| - Telemetry and audit pipeline feeding Security/Observability stacks. | ||||
|  | ||||
| ## Integrations & dependencies | ||||
| - Signer/Attestor for PoE and OpTok introspection. | ||||
| - CLI/UI for login flows and token management. | ||||
| - Scheduler/Scanner for machine-to-machine scope enforcement. | ||||
|  | ||||
| ## Operational notes | ||||
| - MongoDB for tenant, client, and token state. | ||||
| - Key material in KMS/HSM with rotation runbooks (see ./operations/key-rotation.md). | ||||
| - Grafana/Prometheus dashboards for auth latency/issuance. | ||||
|  | ||||
| ## Related resources | ||||
| - ./operations/backup-restore.md | ||||
| - ./operations/key-rotation.md | ||||
| - ./operations/monitoring.md | ||||
| - ./operations/grafana-dashboard.json | ||||
|  | ||||
| ## Backlog references | ||||
| - DOCS-SEC-62-001 (scope hardening doc) in ../../TASKS.md. | ||||
| - AUTH-POLICY-20-001/002 follow-ups in src/Authority/StellaOps.Authority/TASKS.md. | ||||
|  | ||||
| ## Epic alignment | ||||
| - **Epic 1 – AOC enforcement:** enforce OpTok scopes and guardrails supporting raw ingestion boundaries. | ||||
| - **Epic 2 – Policy Engine & Editor:** supply policy evaluation/principal scopes and short-lived tokens for evaluator workflows. | ||||
| - **Epic 4 – Policy Studio:** integrate approval/promotion signatures and policy registry access controls. | ||||
| - **Epic 14 – Identity & Tenancy:** deliver tenant isolation, RBAC hierarchies, and governance tooling for authentication. | ||||
		Reference in New Issue
	
	Block a user