Route get_space — a space is a graph, and nothing told agents to read it - #8
Open
A-PachecoT wants to merge 2 commits into
Open
Route get_space — a space is a graph, and nothing told agents to read it#8A-PachecoT wants to merge 2 commits into
A-PachecoT wants to merge 2 commits into
Conversation
…elling agents to read it get_space already returns the tree, the landing slug, and the link graph with resolved and pending edges. It is exactly the map an agent needs to know where a new doc belongs and what should point at it — and neither the skill nor the flow mentioned it. Same shape as the CLI-vs-MCP fix: the capability existed, the routing did not. Measured on a real space (cofoundy/atelier, 41 docs): - landing_slug was null, so the space opened as a list of 41 titles with no front door - every tree node came back isFolder:false — no folder is a node (cofoundy/basalt#472) - the readme was the only doc with outbound edges Three changes: - get_space becomes step 2 of the MCP flow: read the map BEFORE authoring into it. - a new 'link it into the graph' step, because that is the one that decays silently — every unlinked doc turns the space back into a flat list only search can reach. - SKILL.md gains a short 'a space is a graph, not a folder' section plus one anti-pattern (don't publish an orphan), stated once and applying to both paths. Made measurable rather than a matter of taste: get_space reports edges against nodes, and on the CLI side --strict already fails on unresolved links. SKILL.md 387 -> 512 words (original before this branch series: 666). Tests 26/26, validate-skills ok.
…egla Segunda palanca del incentivo (la primera vive en el generador: harvest.py ahora emite KPIBoard/DonutChart/MetadataCard en vez de tablas planas, así el formato bueno sale gratis y nadie tiene que acordarse). Acá va la que sí es de la skill: antes de autorar, si el doc lleva datos, leer basalt://reference/components y elegir por forma. Markdown tables pasan a ser el fallback explícito, no el default silencioso. Con la razón correcta, que el cookbook no enuncia (cofoundy/basalt#476): los componentes usan var(--cf-*) y se re-skinean por tenant; el markup estilizado a mano no. Un doc con color hardcodeado se ve roto el día que un cliente tenga su propia marca. No es una prohibición: la prosa sigue siendo prosa, y un componente se usa cuando el contenido tiene una forma que la prosa no expresa — no para decorar un párrafo.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
get_spacealready returns the tree, the landing slug, and the link graph (resolved + pending edges). It is exactly the map an agent needs — and neither the skill nor the flow mentioned it.Same shape as #6: the capability existed, the routing did not.
Measured on a real space
cofoundy/atelier, 41 docs published:landing_slugnull— the space opened as a list of 41 titles, no front doorisFolder: false— no folder is a node (cofoundy/basalt#472)readmeChanges
get_spacebecomes step 2 of the MCP flow — read the map before authoring into it.Made measurable rather than a matter of taste:
get_spacereports edges against nodes, and--strictalready fails the CLI publish on unresolved links.Size
SKILL.md 387 → 512 words (before this branch series: 666). Tests 26/26,
validate-skills.shok.Related: cofoundy/basalt#475 (landing inference), #472 (folders as nodes).