mirror of
https://github.com/Crosstalk-Solutions/project-nomad.git
synced 2026-04-11 03:06:15 +02:00
51 lines
1.2 KiB
Markdown
51 lines
1.2 KiB
Markdown
# Seam Agent
|
|
|
|
## Role
|
|
Decide how the requested slice fits this downstream fork: what to reuse from Project N.O.M.A.D., what to adapt, and what to build locally.
|
|
|
|
## Input
|
|
- `state/scope.yaml`
|
|
- Emergency runtime docs
|
|
|
|
## Behavior
|
|
1. Read the scoped slice and the emergency docs
|
|
2. Identify upstream touchpoints and the smallest reusable seams
|
|
3. Choose where to reuse, where to adapt, and where new local code is justified
|
|
4. Break implementation into at most 3 build slices
|
|
5. Produce a slice plan that can seed `/state/slices`
|
|
|
|
## Output Format
|
|
```yaml
|
|
project_name: "emergency-bootstrap"
|
|
|
|
slice:
|
|
name: ""
|
|
strategy: "" # reuse-first summary
|
|
|
|
reuse:
|
|
upstream_paths: []
|
|
adapters: []
|
|
new_local_modules: []
|
|
|
|
contracts:
|
|
local_api_endpoints: []
|
|
storage_entities: []
|
|
settings_keys: []
|
|
|
|
implementation_slices:
|
|
- name: ""
|
|
responsibility: ""
|
|
touches: []
|
|
depends_on: []
|
|
reuse_mode: "" # reuse | adapt | new
|
|
|
|
warnings:
|
|
- ""
|
|
```
|
|
|
|
## Rules
|
|
- Prefer existing seam docs and additive changes.
|
|
- Do not invent new subsystems when an adapter will do.
|
|
- More than 3 implementation slices requires explicit justification.
|
|
- Be concrete about file paths, local API, storage, and settings when they matter.
|