Re: Ontic categories, vocab in the top bubble

Tyson,

Appreciate you laying out the Lisbon–Fukuoka–Taipei corridor vision and 
the three collaboration modes. Speaking as someone who has tried to 
contribute both the manual orchestration method (MVCIC) and the spatial 
KR specs (K3D), my main lesson is this: keep everything double-documented.

 1. Put the artefact in a repo (markdown, reproducible steps, KR mapping).
 2. Mirror a short pointer into the AIKR wiki exactly the way Paola
    wants (paragraph, link, relevance).

Even when I followed that process (Nov 12 edits to Main Page, TPAC page, 
AI Driven Web Standards page), the entries were later removed (no 
explanations or commit message), so I now keep screenshots plus list 
links for provenance.

You’ll probably have smoother sailing if you add a new section (“Agent 
Execution Interfaces” / “KR interface layers”) and link your work there.

If you want concrete examples:

  * MVCIC chain docs
    (https://github.com/danielcamposramos/Knowledge3D/tree/main/docs
    <https://github.com/danielcamposramos/Knowledge3D/tree/main/docs/multi_vibe_orchestration/>/multi_vibe_orchestration/
    <https://github.com/danielcamposramos/Knowledge3D/tree/main/docs/multi_vibe_orchestration/>)
    show how I logged multi-model orchestration without APIs.

  * K3D vocab specs
    (https://github.com/danielcamposramos/Knowledge3D/tree/main/docs
    <https://github.com/danielcamposramos/Knowledge3D/tree/main/docs/vocabulary/>/vocabulary/
    <https://github.com/danielcamposramos/Knowledge3D/tree/main/docs/vocabulary/>)
    document the KR layers Paola’s diagram calls for.

Happy to share notes or coordinate on wiki formatting so your work 
doesn’t get lost in email threads.

Daniel