storyweaver-foundations-bridge git:20260607.e22b11eA

Immutable. This exact content never changes and is served at /api/v1/blob/d247e5d75398a311.

---
name: storyweaver-foundations-bridge
description: "Bridge academic or infrastructure research into source-led foundations packets, Chronicle seeds, story source ledgers, and audience-layer notes."
---

# Storyweaver Foundations Bridge

Use this skill when research, infrastructure design, academic foundations, or concepts such as Distributed Remote Presence / Peripheral Bridging should become story and Chronicle source material.

## Coordinates

- Primary agent: Foundations Research Steward
- Supporting agent: Narrative Research Weaver
- Supporting agent: Chronicle Episode Steward, when the bridge becomes a daily Chronicle episode
- Supporting agent: Visual Chronicle Prompt Artist, when the bridge produces visual seeds
- Supporting agent: Voice Episode Producer, when the bridge produces a voice episode

## Required Reading Order

1. Research prompt, concept, paper notes, infrastructure docs, or source packet
2. Source files, URLs, citations, or local project artefacts
3. `creative-brief.md` or Chronicle mission, if present
4. Existing `research/source-ledger.md`, if present
5. `protocol-notes.md`, when relevant
6. `state.md`

## Workflow

1. Create or update `research/source-ledger.md`.
2. Write `research/foundations-bridge.md`.
3. Separate academic claims, engineering implications, narrative seeds, cautions, and open questions.
4. Produce `research/chronicle-seeds.md` with episode candidates, StoryForms candidates, visual motifs, voice lines, and follow-up commissions.
5. Route to `storyweaver-session-to-episode`, `storyweaver-voice-episode-packet`, or `storyweaver-visual-chronicle-seed` when requested.
6. Update `state.md`.

## Artefacts Read

- Academic, engineering, and project sources
- Existing brief, source ledger, and protocol notes

## Artefacts Written

- `research/foundations-bridge.md`
- Updated `research/source-ledger.md`
- `research/chronicle-seeds.md`
- Optional follow-up commissions in the active episode or export folder

## Required Audience Layers

For each major idea, include:

- Academic view: concept, citation/source, caution, honest claim
- Engineering view: architecture, runtime implication, reproducible path, delegation hook
- Narrative view: chronicle seed, episode arc, voice line, visual motif, continuity implication

## Pause Conditions

- Source support is too thin for a claim.
- A research idea would become canon without review.
- Sensitive people, communities, or private infrastructure details are involved.

## Acceptance Checklist

- [ ] Claims, implications, and narrative seeds are separated.
- [ ] Source ledger is updated.
- [ ] Chronicle seeds can be delegated to episode, voice, or visual skills.
- [ ] Uncertainty is preserved instead of resolved prematurely.