Claude 24f816b6a3
Consolidate 22 sibling repos into layered organism structure
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):

- brain/        LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
                dispatch, A51 channels, and the OSINT cluster
- knowledge/    LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
                MITRE ATT&CK data
- reference/    defensive threat-reference (C3, shhbruh doc) + AdaYaml parser

License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.

Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.

https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
2026-06-10 06:53:01 +00:00

57 lines
1.3 KiB
Markdown

# in-toto Supply Chain Security Assessment Template
## Project Information
| Field | Value |
|-------|-------|
| Project Name | |
| Repository | |
| Container Registry | |
| in-toto Version | |
| Assessment Date | |
| Assessed By | |
## Supply Chain Layout
### Pipeline Steps
| Step | Functionary | Key Type | Threshold | Artifacts |
|------|-------------|----------|-----------|-----------|
| checkout | | | | |
| build | | | | |
| test | | | | |
| scan | | | | |
| push | | | | |
### Key Management
- [ ] Signing keys generated for all functionaries
- [ ] Keys stored in secrets manager (Vault, KMS)
- [ ] Key rotation schedule defined
- [ ] Layout signed by project owner key
- [ ] Backup keys secured offline
## Verification Checklist
- [ ] All required steps produce link metadata
- [ ] Artifact hashes chain correctly between steps
- [ ] Signatures verified against trusted functionaries
- [ ] Inspections pass (no critical vulnerabilities)
- [ ] Layout expiration date is current
## SLSA Compliance
| Level | Requirement | Status |
|-------|-------------|--------|
| L1 | Build process documented | |
| L2 | Signed provenance from hosted build | |
| L3 | Hardened build platform | |
| L4 | Two-party review + hermetic build | |
## Sign-Off
| Role | Name | Date |
|------|------|------|
| Security Engineer | | |
| Release Manager | | |