82a358f18d
ontoref-derive: #[onto_mcp_tool] attribute macro registers MCP tool unit-structs in
the catalog at link time via inventory::submit!; annotated item is emitted unchanged,
ToolBase/AsyncTool impls stay on the struct. All 34 tools migrated from manual wiring
(net +5: ontoref_list_projects, ontoref_search, ontoref_describe,
ontoref_list_ontology_extensions, ontoref_get_ontology_extension).
validate modes (ADR-018): reads level_hierarchy from workflow.ncl and checks every
.ncl mode for level declared, strategy declared, delegate chain coherent, compose
extends valid. mode resolve <id> shows which hierarchy level handles a mode and why.
--self-test generates synthetic fixtures in a temp dir for CI smoke-testing.
validate run-cargo: two-step Cargo.toml resolution — workspace layout first
(crates/<check.crate>/Cargo.toml), single-crate fallback by package name or repo
basename. Lets the same ADR constraint shape apply to workspace and single-crate repos.
ontology/schemas/manifest.ncl: registry_topology_type contract — multi-registry
coordination, push targets, participant scopes, per-namespace capability.
reflection/requirements/base.ncl: oras ≥1.2.0, cosign ≥2.0.0, sops ≥3.9.0, age
≥1.1.0, restic declared as Hard/Soft requirements with version_min, check_cmd, and
install_hint (ADR-017 toolchain surface).
ADR-019: per-file recipient routing for tenant isolation without multi-vault. Schema
additions: sops.recipient_groups + sops.recipient_rules in ontoref-project.ncl.
secrets-bootstrap generates .sops.yaml from project.ncl in declarative mode. Three
new secrets-audit checks: recipient-routing-coherent, recipient-routing-coverage,
no-multi-vault. Adoption templates: single-team/, multi-tenant/, agent-first/.
Integration templates: domain-producer/, mode-producer/, mode-consumer/.
UI: project_picker surfaces registry badge (⟳ participant) and vault badge
(⛁ vault_id · N, green=declarative / amber=legacy) per project card. Expanded panel
adds collapsible Registry section with namespace, endpoint, and push/pull capability.
manage.html gains Runtime Services card — MCP and GraphQL toggleable without restart
via HTMX POST /ui/manage/services/{service}/toggle.
describe.nu: capabilities JSON includes registry_topology and vault_state per project.
sync.nu: drift check extended to detect //! absence on newly registered crates.
qa.ncl: six entries — credential-vault-best-practice (layered data-flow diagram),
credential-vault-templates (paths A/B/C), credential-vault-troubleshooting (15 named
errors), integration-what-and-why (ADR-042 OCI federation), integration-how-to-implement,
integration-troubleshooting.
on+re: core.ncl + manifest.ncl updated to reflect OCI, MCP, and mode-hierarchy nodes.
Deleted stale presentation assets (2026-02 slides + voice notes).
3.7 KiB
3.7 KiB
Presentation Docs — Index
Material de referencia para posts, slides y presentaciones de ontoref.
Análisis y posicionamiento ontoref
| Archivo | Contenido |
|---|---|
| ontoref-yin-yang-diferenciacion.md | Por qué Talisman no resuelve el lado operacional. Ontología sin Reflection = buenas intenciones. |
| ontoref-dags-diferenciacion.md | Por qué los DAGs de ontoref son distintos a CI/CD, compiladores, runbooks. DAGs como conocimiento vs. ejecución. |
| ontoref-scope-proyecto-infra-personal.md | Scope completo: proyecto + infraestructura + personal. Stack soberano: jj, Radicle, NATS, CLI/UI/MCP/GraphQL. |
Posts — Serie ontoref (EN + ES)
Publicados en jesusperez.pro/blog. Estado: borradores (published: false).
| Post | EN | ES |
|---|---|---|
| AI is a knowledge tool — who keeps it alive? | en | es |
| DAGs are everywhere — none know what they are | en | es |
| One protocol, three subjects | en | es |
| Your ontology should live with your code | en | es |
Fuentes externas — Talisman (KGC 2026)
| Archivo | Contenido |
|---|---|
| Steal_This_Deck.pdf | Deck completo. "Stop Betting, Start Building", KGC 2026, Jessica Talisman. |
| talisman-steal-this-deck-extractions.md | Extracciones del deck: citas, datos citable, mapeos a ontoref, nota de atribución. |
| talisman-article/ | Artículo de Talisman "A Two-Week Sprint for Knowledge" en EN/ES, PDF y Typst. |
Fuentes externas — José Celano
| Archivo | Contenido |
|---|---|
| JoseCelano_2026-6-08_Ontologías_y_DAGs.pdf | Ontologías y DAGs — presentación José Celano, junio 2026. |
Material previo — ontología como filosofía del software
| Archivo | Contenido |
|---|---|
| ontologia-filosofia-software.md | Documento principal: ontología como fundamento filosófico del software. |
| ontologia-filosofia-software.pdf | Versión PDF. |
| ontologia-filosofia-software.typ | Fuente Typst. |
| ontologia_motor.md | Ontología como motor — concepto central. |
| ontologia_motor_resumen.md | Resumen ejecutivo del motor ontológico. |
Material previo — sprints y contexto
| Archivo | Contenido |
|---|---|
| 2-week-sprint-knowledge_done.md | Sprint de dos semanas para conocimiento — completado. |
| about_plantir.md | Contexto sobre Plantir como referencia de posicionamiento. |
| 2026-02-17-notas_voz.md | Notas de voz, 17 Feb 2026. |
| 2026-02-27-notas_voz_rust.md | Notas de voz sobre Rust, 27 Feb 2026. |
| 2026-04-24-234910-me-planteo-estas-dos-propuestas-para-un-open-spac.txt | Propuestas para open space, 24 Abr 2026. |
| 2026-04-25-000346-puedes-sacar-el-texto-de-este-contenido.txt | Extracción de contenido, 25 Abr 2026. |