PopSoc Deploy Engine: Gist-to-Infographic skill architecture and protocol pin/canvas flow (public)

meta-gist-popsoc-infographic-skill-architecture.md

PopSoc Deploy Engine: Gist → Infographic Skill Architecture (Meta Gist)

What this skill does exactly

The gist-to-infographic skill converts one or more GitHub gists into a deployment-ready infographic artifact for PopSoc.

It does 3 jobs:

1. Evidence Extraction

   • Pull gist files.
   • Extract factual evidence lines (headings, bullets, metrics, protocol statements).
   • Remove weak/noisy lines.

2. Narrative + Style Compilation

   • Choose an infographic archetype (systems map, timeline, KPI dashboard, executive brief, etc.).
   • Choose a style preset (boardroom, swiss minimal, CRT, retro comic, industrial blueprint).
   • Emit NotebookLM-ready prompt instructions with orientation/detail controls.

3. Protocol Deployment (PopSoc Engine)

   • Publish as an infographic canvas card with UUIDv8 IDs.
   • Register as canvas pin in protocol layer.
   • Make card discoverable through /api/portal/cards feed.

Why this matters for PopSoc

This turns research and protocol notes (usually trapped in docs/gists) into operational visual assets that can be:

• shown on map/canvas surfaces,
• attached to venues/events/workflows,
• replayed as deploy artifacts,
• tracked via deterministic UUID envelopes.

Runtime architecture

A) Build phase

Endpoint: POST /api/popsoc/infographic/build

Input:

• gist_ids[]
• optional title, city_spoc, archetype, style_preset_id, notebooklm_controls

Output:

• build_uuid_v8
• gist_brief_markdown
• notebooklm_prompt_markdown
• selected archetype/style/controls
• extracted evidence lines

Persistence:

• data/popsoc-infographic-builds.json

B) Publish phase

Endpoint: POST /api/popsoc/infographic/publish

Input:

• build object (or gist ids to auto-build)
• optional pin placement (lat, lng, layer, venue_id)

Output:

• published portal card object
• published canvas pin object

Persistence:

• cards: data/popsoc-infographics.json
• pins: data/popsoc-canvas-pins.json

C) One-shot deploy

Endpoint: POST /api/popsoc/infographic/deploy

Behavior:

• build + publish in one call.

UUIDv8 protocol mapping

The deploy engine uses deterministic UUIDv8 generation:

• TYPE_CONTENT.PORTAL_CARD (0x2d1) for published card shell
• TYPE_CONTENT.CARD_CONFIG_TYPE (0x2d2) for card config shell
• TYPE_INFORMATION.INFOGRAPHIC (0x603) for infographic entity/build identity
• TYPE_INFORMATION.SIGN_PLACEMENT (0x602) for protocol pin/placement
• temporal envelope IDs from the same block:
  • INFO_MESSAGE (0x604)
  • INFO_SCHEDULE (0x606)
  • INFO_WINDOW (0x607)
  • INFO_REVISION (0x609)
  • INFO_RENDER (0x60A)
  • INFO_DISTRIBUTION (0x60E)

Domain:

• DOMAIN.CONTENT (0x1)

Namespace:

• hash of city_spoc

This keeps infographic assets first-class in the same protocol graph as venues/cards/actions/payments.

Integration points

• /api/portal/cards now merges static cards + deployed PopSoc infographic cards.
• /api/popsoc/canvas/pins exposes canvas pin feed.
• Existing kiosk/canvas UIs can consume these cards without schema changes.

Quality and safety guarantees

• Evidence-grounded prompts: no invented stats by default instruction.
• One-message visual discipline per artifact.
• Explicit unknowns where evidence is weak.
• Style and archetype are declarative, versionable, and replaceable.

Forward roadmap

1. Add provider adapters (NotebookLM/Gemini/other renderers) behind a pluggable interface.
2. Auto-select archetype via richer classifier (domain + intent + audience).
3. Add provenance links from infographic card back to contract/payment events.
4. Add x402/paywall hooks for premium infographic feeds.

---

Summary: This is no longer "prompt hacking". It is a protocol-native visual deployment system: Gists in → Evidence graph → Infographic build → Canvas card + Pin out.