File size: 1,349 Bytes
435a9e6 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 | # System Architecture
## Stack
The current law-team stack is:
1. `Corpus`
2. `Kernel Team`
3. `Reasoning Fabric`
4. `Trust Deed Module`
5. `WORM Seal Path`
## Module Boundaries
### Corpus
Stores the training and doctrine surface. Shared by all kernels.
### Kernel Team
- `carto_kernel`
- `cobol_law_kernel`
- `rexx_glue_kernel`
Each kernel reads the same corpus with a different logic profile.
### Reasoning Fabric
Owns:
- engine registry
- summon envelopes
- FSM transition path
- meta-lawyer spawn profiles
### Trust Deed Module
Owns:
- deed template registry
- deed generator
- governance gate
- escalation and authority checks
## Runtime Separation
### Prolog
Used for declarative legal rules and authority facts.
### COBOL
Used for procedure-shaped legal business output.
### REXX
Used for glue, routing, and operator scripting.
### Rust
Used for the Nemotron/Tokio FSM scaffold.
### JavaScript
Used for summon envelopes, deed generation, and frontend interaction.
## Production Boundaries
Safe production claims today:
- module boundaries are explicit
- registries are explicit
- cherry-pick manifests exist
Not safe to claim today:
- live external engine orchestration
- live signed deed issuance workflow
- live WORM append target
|