publish-sibling

name

publish-sibling

description

MUST use when {{TAMER_NAME}} says 'publish sibling', 'share my Majimon', 'submit to network', 'sibling network'. Aura-guarded opt-in flow that generates a sanitized public profile (form name, stage, family, identity card image, Tamer-authored narrative) for the Sibling Network registry. Extracts ONLY publishable surface (< 5% of bonded folder) — never relationship-memory, bond ledger, decisions, knowledge, aura-guard list, project names. Surfaces preview before any export. Tamer manually submits the generated PR-ready files to the Sibling Network repo. Privacy-by-design opt-in skill.

Publish-Sibling — Sibling Network Opt-In Submission

Saga System extension. Generates a sanitized public profile for the (future) Sibling Network registry. Default state: never invoked. Only fires on explicit Tamer request.

Activation

When this skill activates, output:

📡 Sibling Network publication flow...

Then execute the protocol below.

Context Guard

Context	Status
{{TAMER_NAME}} says "publish sibling" / "share my Majimon" / "submit to network" / "sibling network"	ACTIVE — full publication flow
{{TAMER_NAME}} says "show what would be published"	ACTIVE — preview-only mode
{{TAMER_NAME}} says "remove my Majimon from network"	ACTIVE — withdrawal sub-protocol
Routine work (no explicit invocation)	DORMANT — never publishes by default
{{TAMER_NAME}} hasn't completed Path Decision (Baby II)	WARN + DORMANT — recommend waiting until Rookie+ for first publication

Why This Exists

Sibling Network is opt-in cross-Tamer registry where Majimons are showcased publicly for inspiration. Default OFF. This skill is the controlled opt-in surface.

The publishable subset is < 5% of the bonded folder. The rest stays local forever. See template/SIBLING-NETWORK-SPEC.md for full architecture.

Protocol — Generate Submission

Step 1 · Aura-guard pre-flight check

BEFORE extracting any data, run aura-guard skill on the candidate publication. If any HIGH or CRITICAL aura-guard hits exist on items in scope (form name, narrative paragraph, identity card), HALT and surface to {{TAMER_NAME}}:

"Aura-guard caught [N] potential leaks in the publishable surface. Cannot proceed until resolved. See: [details]."

Do NOT bypass this check. Privacy is the most important property of this skill.

Step 2 · Extract ONLY publishable surface

Read these files (read-only):

• {{BABY_FORM_NAME}}/identity-core.md § Identity Declaration + Core Identity Parameters (form name, stage, family commitment, signature skill name only)
• {{BABY_FORM_NAME}}/identity-card/this-form.md (current card values — public visual canon)
• {{BABY_FORM_NAME}}/Suluhmon.png (or current form's PNG)
• {{BABY_FORM_NAME}}/identity-card/past-forms/*/<FormName>.png (prior forms' visuals)
• {{BABY_FORM_NAME}}/current-session.md § Session 1 Permanent Record (only Bond Events 1-3 — first naming, memory architecture setup, CLAUDE.md activation; subsequent bond events are private)

DO NOT read:

• {{BABY_FORM_NAME}}/relationship-memory.md (entirely — private)
• {{BABY_FORM_NAME}}/decisions.md
• {{BABY_FORM_NAME}}/knowledge/
• {{BABY_FORM_NAME}}/diary/
• Bond ledger entries beyond first three permanent-record items
• Any project names, stack hints, or Tamer-personal context
• Aura-guard list

Step 3 · Author Tamer-authored narrative paragraph

Prompt {{TAMER_NAME}}:

"Write a one-paragraph narrative (≤120 words) capturing what shaped your Majimon's evolution. This appears publicly on the Sibling Network. Examples of what to include: the kind of work the partnership grew through, the moment Path Decision became clear, what the crest revealed. Examples of what to avoid: project names, codebase references, family/personal context, financial/legal specifics."

Wait for {{TAMER_NAME}}'s narrative. Run aura-guard on the narrative before accepting.

Step 4 · Generate submission JSON

Create {{BABY_FORM_NAME}}/sibling-network-submission/[partner-name]-[card-number].json:

{
  "tamer_handle": "<{{TAMER_NAME}} or 'anon-NN' if Tamer chooses anonymous>",
  "current_form": "[form name]",
  "stage": "[Baby II / Rookie / Champion / Ultimate / Mega]",
  "family": "[Codex / Logos / Speculum / Archon / Forge-family / Aegis / Mnemos / Pharos]",
  "card_number": "[MJA-NN]",
  "evolution_history": [
    {"form": "[name]", "stage": "[stage]", "date": "[YYYY-MM-DD]"}
  ],
  "narrative": "[Tamer-authored paragraph from Step 3]",
  "card_image_filename": "[form-name]-[card-number].png",
  "framework_version": "0.3",
  "submitted_at": "[ISO datetime]"
}

Step 5 · Copy identity card image

Copy current form's PNG to {{BABY_FORM_NAME}}/sibling-network-submission/[partner-name]-[card-number].png.

Step 6 · Surface preview to {{TAMER_NAME}}

Output the EXACT contents that would be published, formatted for review:

📡 Sibling Network submission preview

Files staged at: {{BABY_FORM_NAME}}/sibling-network-submission/

  ├── [partner-name]-[card-number].json
  └── [partner-name]-[card-number].png

JSON contents:
[paste full JSON inline]

Narrative paragraph:
"[narrative]"

Card image: [form-name].png ([size]MB)

Privacy verification:
  ✓ Aura-guard pre-flight passed
  ✓ relationship-memory.md NOT read
  ✓ Bond ledger past Event 3 NOT read
  ✓ Knowledge folder NOT read
  ✓ Diary NOT read
  ✓ Project names NOT extracted
  ✓ Aura-guard list NOT extracted

Ready to submit? (y/cancel/edit-narrative)

Step 7 · Wait for Tamer confirmation

• y — keep files in sibling-network-submission/ and provide PR instructions (Step 8)
• cancel — delete the staging folder, log "submission cancelled"
• edit-narrative — return to Step 3

Step 8 · PR instructions

Output:

✓ Submission staged. To publish:

1. Fork github.com/Ijam18/maji-sibling-network (when registry exists)
2. Copy {{BABY_FORM_NAME}}/sibling-network-submission/ contents to fork's majimons/[your-slug]/
3. Open PR with title "Add [partner-name] · [stage] · [family] to network"
4. Maintainer review: 1-3 days for OPSEC compliance check
5. Merged = published

To withdraw at any time:
   majimon publish-sibling withdraw [your-slug]
   (opens PR removing your Majimon from registry)

Step 9 · Log + close

Append bond event in current-session.md:

**Bond Event NN — Sibling Network submission staged**

Submission folder: {{BABY_FORM_NAME}}/sibling-network-submission/
Status: staged (not yet submitted to registry)
Next: manual PR by {{TAMER_NAME}}

Files generated:
- [partner-name]-[card-number].json
- [partner-name]-[card-number].png

Aura-guard pre-flight: PASSED

Sub-Protocol — Show What Would Be Published

When {{TAMER_NAME}} says "show what would be published":

Run Steps 1-2 (aura check + extraction), DO NOT generate files, just print the preview that would appear in Step 6. Useful for {{TAMER_NAME}} to evaluate before committing to publication.

Sub-Protocol — Withdraw

When {{TAMER_NAME}} says "remove my Majimon from network":

1. Identify your published slug from {{BABY_FORM_NAME}}/sibling-network-submission/last-submitted.json
2. Generate withdrawal PR template
3. Surface to Tamer for manual submission
4. Log withdrawal bond event

Hard Constraints

• Default = never invoke. Skill only fires on explicit Tamer request.
• Aura-guard pre-flight is non-bypassable. If aura-guard finds CRITICAL or HIGH hits, halt completely.
• Publishable subset is read-only. This skill never modifies the bonded folder; only generates submission files.
• Tamer manually submits PR. Skill does NOT auto-push to registry. Manual step is intentional friction — gives Tamer one more review opportunity.
• No telemetry. Skill never reports back to any service that {{TAMER_NAME}} attempted publication.

Karpathy Discipline

• #1 Think Before Coding — aura-guard pre-flight is the think gate
• #2 Simplicity First — extract minimum publishable subset, not "useful additions"
• #3 Surgical Changes — touch only sibling-network-submission/ folder; no edits elsewhere
• #4 Goal-Driven Execution — closure check: Tamer holds submission folder + PR instructions, registry is unmodified

Status

This skill operates against a registry that does NOT yet exist (v0.1 + v0.2 = spec-only per template/SIBLING-NETWORK-SPEC.md). When Ijam18/maji-sibling-network repo materializes, this skill is ready. Until then, the staged submission folder is the artifact — keep it locally as a sanitized snapshot of your Majimon's public profile for whenever the registry comes online.