Register kings-guard with State Hub
This commit is contained in:
parent
1075f18a1a
commit
42dfd27886
10 changed files with 3714 additions and 0 deletions
66
SCOPE.md
Normal file
66
SCOPE.md
Normal file
|
|
@ -0,0 +1,66 @@
|
|||
# SCOPE
|
||||
|
||||
> Lightweight boundary for agents and contributors.
|
||||
|
||||
---
|
||||
|
||||
## One-liner
|
||||
|
||||
Adaptive security assessment and bounded-response layer for multi-tenant cloud
|
||||
platforms.
|
||||
|
||||
---
|
||||
|
||||
## Core Idea
|
||||
|
||||
`kings-guard` turns declared healthy intent plus observed runtime behavior into
|
||||
posture judgments, typed security signals, and bounded response requests. It
|
||||
consumes evidence from identity, authorization, secret, and runtime systems
|
||||
without replacing those systems' primary authority.
|
||||
|
||||
---
|
||||
|
||||
## In Scope
|
||||
|
||||
- Canonical terminology and contracts for security genome, phenotype,
|
||||
observation, signal, effector, tolerance, inflammation, and immune memory.
|
||||
- Reference architecture and boundary documents for adaptive defense in
|
||||
multi-tenant and agent-active environments.
|
||||
- Minimal posture-evaluation loop design: ingest observations, compare against
|
||||
intended healthy state, and emit typed posture/signal results.
|
||||
- Integration seams to adjacent security systems such as `key-cape`,
|
||||
`flex-auth`, `secrets-engine`, `ops-warden`, and the Railiance runtime
|
||||
layers.
|
||||
- Non-secret evidence, workplans, and repo-operational metadata.
|
||||
|
||||
---
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- Identity issuance, login, MFA, or token minting.
|
||||
- Authorization policy administration or final resource allow/deny decisions.
|
||||
- Secret custody, lease issuance, or raw secret-value delivery.
|
||||
- Infrastructure provisioning, workload deployment, or cluster/platform
|
||||
operations.
|
||||
- Generic SIEM ownership, ticket tracking, or live work coordination beyond
|
||||
this repo's own workplans.
|
||||
|
||||
---
|
||||
|
||||
## Current State
|
||||
|
||||
- Markdown-first exploration repo. Current canon is `INTENT.md`,
|
||||
`specs/NetKingdomImmuneArchitecture.md`, and `history/InitialExploration.md`.
|
||||
- No executable service, schemas, or integration adapters exist yet.
|
||||
- The first implementation strand should establish canonical contracts and a
|
||||
minimal posture pilot before broader integrations.
|
||||
|
||||
---
|
||||
|
||||
## Getting Oriented
|
||||
|
||||
- Start with: `INTENT.md`
|
||||
- Architecture draft: `specs/NetKingdomImmuneArchitecture.md`
|
||||
- Exploration notes: `history/InitialExploration.md`
|
||||
- Agent instructions: `AGENTS.md`
|
||||
- Workplans: `workplans/`
|
||||
Loading…
Add table
Add a link
Reference in a new issue