feat(fluree-companion): the paved-path rule (1.0.1) - #5
Open
aaj3f wants to merge 1 commit into
Open
Conversation
…can see (1.0.1) First zero-shot field test: the agent found the right concept pages, then assembled its own pipeline from raw primitives — CLI-created ledgers, raw inserts, direct execution calls — and delivered working-but-invisible results: no Uploads entry, no source-document links, no identity annotations. The API permitted it; nothing steered against it. Rule 6 is the rail: if the task matches a story, follow the story's sequence end-to-end (ordering is usually the point); go off-path only when no story fits, and say so with the cost named; never substitute the platform's source code for its docs when a repo happens to be in the working directory. Done-ness test: can the user see what was built in the UI right now — files, sources, links. stories.md frames its routes as paved paths explicitly.
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.
Part of #3 — the first correction from field evidence.
The first zero-shot smoke test against a live stack surfaced a steering failure the plugin's doctrine didn't cover: the agent fetched the right concept pages, then assembled its own pipeline from raw primitives (CLI-created ledgers, raw inserts, direct execution calls) and produced working-but-invisible results — no Uploads-surface presence, no source-document links, no identity-graph annotations. Everything it did was permitted; nothing steered it toward the sequence the product means.
Rule 6 names the failure mode and the rail: story-first (the how-to's ordering is usually the point — identity mappings exist before extraction so the run can ground against them), off-path only when no story fits and only out loud with the cost stated, and never source-code-as-docs when a Fluree repo happens to be visible in the working directory. The done-ness test it teaches: can the user see what was just built in the UI — the files, the sources, the links?
stories.mdnow frames its routes as paved paths explicitly.This is the doctrine half; the systematic half (paved-path playbooks per story + the anti-path inventory over the ~300 story-less routes) is the steering axis being folded into the C5 audit sweep on fluree/solo#1040.
Validation:
claude plugin validategreen, version-sync green (fluree-companion 1.0.1).