메뉴
Checkpoint -- route stash items, write log entry, update bundle, trigger projection, reset stash
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | alive-save |
| description | Checkpoint -- route stash items, write log entry, update bundle, trigger projection, reset stash |
| version | 1.0.0 |
| author | ALIVE Context System |
| license | MIT |
| toolsets | ["terminal","file"] |
| triggers | ["save","checkpoint","let's save","stash is heavy"] |
| metadata | {"hermes":{"tags":["ALIVE","context","save","checkpoint"]}} |
Route the stash, write the log, update the bundle, trigger projection.
Stash (N items):
Decisions:
1. [decision] -> [walnut]
2. [decision] -> [walnut]
Tasks:
3. [task] -> [walnut]
Notes:
4. [note] -> [walnut]
5. [note] -> [[person]]
Confirm, edit, or drop items?
Prepend to _kernel/log.md after frontmatter. Use terminal:
# Read existing log, prepend new entry after frontmatter
Entry format:
## YYYY-MM-DDTHH:MM:SS -- squirrel:[session_id]
**Type:** [feature/decision/research/strategy/etc]
[Narrative paragraph -- what happened, why, what it means]
### Decisions
- [decision with rationale]
### Artifacts
- [files created/modified]
signed: squirrel:[session_id]
Write to the active bundle's context.manifest.yaml:
context: field with current statestatus: if changedConfirmed task-shaped stash items are promoted in a single batch via alive tasks promote after the squirrel YAML stash is written. The CLI walks each type: task stash item, writes the task row, and stamps promotion_state / task_id markers back onto the squirrel file under a single flock for crash safety.
"$ALIVE_PLUGIN_ROOT/bin/alive" tasks promote \
--squirrel "[session_id]" \
--walnut "[path]"
Python fallback if bin/alive is missing:
"${ALIVE_PYTHON:-python3}" "$ALIVE_PLUGIN_ROOT/scripts/cli.py" tasks promote \
--squirrel "[session_id]" --walnut "[path]"
For non-promotion edits on existing tasks (mark done, change priority), use tasks.py directly:
python3 "$ALIVE_PLUGIN_ROOT/scripts/tasks.py" done --walnut "[path]" --id "[task_id]"
Never read or write tasks.json directly. Fail-loud if the CLI binary is missing on both paths — do not fall back to per-item adds from the agent.
Stash items tagged with [[person-name]] get dispatched to person walnuts as brief log entries.
The post-save hook triggers project.py to regenerate now.json. This is automatic.
Update _kernel/log.md frontmatter:
last-entry: timestampentry-count: incrementsummary: one-line summaryAsk: "If a new agent loaded this walnut with no context, would it have everything it needs?"
If no, fix the log entry or manifest before finishing.
"Any bundles worth sharing?"
Stash clears. Session continues.
Morning briefing -- read all walnut states, surface priorities, inbox count, stale walnuts, people nudges
Morning operating system -- sync inputs, read everything, surface priorities, show the day
Load an ALIVE walnut -- read kernel files, show current state, surface one observation, ask what to work on
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
The human mentions a walnut to work on, asks about a specific venture/experiment/project, or wants to check status — not just explicit 'load X'. Load the brief pack (3 files), resolve the people involved, check the active bundle — then surface one observation and ask what to work on. Context loads in tiers: walnut and people are automatic, bundle depth is offered.