Skip to main content

Brainstorm

Compile presentation instead of authoring it

Accepted direction for artifact delivery, with the alternatives that were weighed.

Compared approaches

Hand-authored HTML per skill

  • Full control over every artifact.
  • Each skill carries its own CSS, JavaScript, and accessibility debt.
  • Presentation drifts between skills over time.

Typed compiler with a Page Spec

  • One implementation of presentation for every skill.
  • Deterministic output, so the same spec yields identical bytes.
  • Offline by default, with no CDN or font fetch.

Delivery flow

Delivery flow

  1. Invoking skillskillthen to specemits
  2. Page Specspecthen to compilercompiles
  3. AK Render compilercompilerthen to artifactwrites
  4. Offline artifactartifact

Rendered as a structured fallback because no diagram adapter is configured.

Open risks

Risk by impact and likelihood
AreaImpactLikelihoodNote
Legacy renderer left alivehighmediumMigrate once and record a removal date for any retained flag.
Facts drift from the narrativemediumlowThe invoking skill keeps factual responsibility; the compiler never invents content.

Unresolved questions

  • Which artifact types migrate after the first wave?
  • Does a hosted share link need its own consent flow?