ontology-field-trial

Featured

Measure Atlas ontology quality on an unfamiliar repository with a source-hidden handoff and four baseline measurements. Use for changes to meaning-construction rules or MCP read/write behavior that can change vault contents, or an explicit ontology-quality field trial. Skip UI work and wording-only clarifications that preserve the evidence, approval, and write contracts.

AI & Automation 139 stars 21 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Field trial — does the vault survive being the only thing you have? This project sells a meaning layer that an agent consumes. The only test of that claim is to **take the source away** and see whether the vault still answers. Everything else — node counts, green checks, a map that looks full — measures effort, not usefulness. Use the [Atlas meta-model specification](../../../docs/ONTOLOGY-ATLAS-SPEC.md#2-the-five-authorable-node-kinds-and-reserved-reader-kind) as the shared answer key for kind, relation, direct `is_a`, and unsupported inference claims. The trial measures whether agents can apply that contract; it must not invent a second rubric from the vault it is judging. Run this as four measurements, in order. Each one produces a number or a list that goes in the report. **Do not skip a phase because the previous one looked good** — phase 1 has looked good every time, and phases 2–4 are where the defects were. ## Before you start Pick a repository **nobody in this session knows**, permissively licensed (Apache-2.0 / MIT / BSD), in a domain you cannot bluff. That is the point: a familiar repository lets the agent — and you — fill gaps from memory, and the whole trial then measures your memory instead of the vault. ⚠️ **Never name the chosen repository in this repo's code, tests, identifiers, fixtures, or commit messages** (`.claude/rules/forbidden.md` — no third-party brands in identifiers). Everything the trial produces lives outside this checkout — a scratch dir...

Details

Author
wlsdks
Repository
wlsdks/ontology-atlas
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

ontology-bootstrap

Build a trustworthy first ontology from an empty or near-empty ontology-atlas vault using only Atlas MCP evidence. Use when the user asks to analyze a codebase, bootstrap/fill its ontology, extract product meaning from a repository, or when a requested ontology task finds only starter nodes. Separate observed implementation facts from proposed meanings, define and cite every domain/capability, answer competency questions, obtain independent source-hidden qualification and user approval, then write only the exact released plan with batch tools. Route mature vaults with 20+ curated nodes to ontology-sync instead; this is a workflow threshold, never a vault or project node limit.

139 Updated today
wlsdks
AI & Automation Listed

trial-run

Plan a scored ERC-26 trial run (procedure, pass criteria, pre-run checklist) or log a completed one with the real point breakdown. Use before running a scored trial, or right after one.

1 Updated 2 weeks ago
Faaz17
Data & Documents Listed

vaultwatch

Set up and operate an AUDITED knowledge vault: a plain-markdown second brain whose claims are verified by two instruments — a no-network coherence audit (the vault against itself) and a world audit (the vault against the running reality it describes: HTTP endpoints, served files, git remotes, on-chain state). Use this whenever the user wants a knowledge base, second brain, vault, wiki, HANDOFF, project memory, or documentation system for a repo that OPERATES something — servers, deployments, published content, prices, wallets, APIs — and also whenever they complain that docs drift, lie, go stale, or that "the README is always wrong". Covers bootstrapping a new vault, retrofitting auditors onto an existing docs/ folder, and the session-close ritual (fix what the session made false, re-run the audits, commit). If the knowledge is pure reading notes with no world that can contradict them, a plain wiki is enough and this skill is overkill.

0 Updated yesterday
yvalenta