code-intelligence
mache
active · public- the question
- How can structured data become navigable rather than merely searchable?
- the primitive
- code as a filesystem you can walk
- record
- Projects code and other structured sources into a navigable graph for tools and filesystems.
position
- reads projections from ley-line-open
- routes navigation for x-ray
declared dependencies how →
- artifactagentic-research/ley-line-open releasesmache/Taskfile.yml
- artifactio.github.agentic-research/ley-line-open 0.13.0mache/server.json
- librarygithub.com/agentic-research/ley-line-open/clients/go/leyline-schema v0.13.0mache/go.mod
Declared, but not asserted. A source names something these repositories are not observed to publish under that name, so the target was identified by matching a name against a convention — true today, and able to go quietly wrong on a rename. Listed rather than dropped, and deliberately excluded from the statements above and from graph.json's edges.
- artifactcanonical-hours → mache — machecanonical-hours/.mache-version — a `.<tool>-version` filename, where the tool name comes from the FILENAME rather than from anything the target declares
- tenancymache → cloister — declares _meta."art.cloister/v1"mache/server.json — a namespaced _meta key whose owner is identified by a constant in this generator
- unresolvedleyline-release.github/workflows — accepts a repository_dispatch event no roster repository is declared to send