[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AP99F574W1MSFPVG81HV9W":3,"skill-same:01M7AP99F574W1MSFPVG81HV9W":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7AP99F574W1MSFPVG81HV9W","lemma",null,"Turn Solidity solc standard JSON inputs or Markdown document trees into validated JSONL chunks with source locations and separate quotation, model, and embedding text. Use when asked to run Lemma, invoke lemma:lemma, prepare Solidity or Markdown for retrieval, generate citation-aware chunks, or inspect Lemma output. Do not use it to embed, index, retrieve, or answer from the chunks.","wildcat-finance\u002Fskills","wildcat-finance","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113041915?v=4","01M7AP0V1G8X0SWHP6C5V90RM5","The Wildcat Protocol","01M7AP0V24Y50BGVCQ4DV496VD",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Flemma\u002Fskills\u002Flemma\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lemma\ndescription: Turn Solidity solc standard JSON inputs or Markdown document trees into validated JSONL chunks with source locations and separate quotation, model, and embedding text. Use when asked to run Lemma, invoke lemma:lemma, prepare Solidity or Markdown for retrieval, generate citation-aware chunks, or inspect Lemma output. Do not use it to embed, index, retrieve, or answer from the chunks.\nmetadata:\n  version: \"0.5.1\"\n---\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"..\u002F..\u002Fassets\u002Fcharacters\u002Flemma.png\" width=\"1200\">\n\u003C\u002Fp>\n\n# Lemma\n\n## Frontier\n\nLemma owns its own chunking and validation frontier, not Hexaemeron's delivery or\nSolidity frontier. Its version, held target, next job, and maturity\nstate live in [EVOLUTION.md](EVOLUTION.md). Do not recommend or run\nanother frontier pass after that ledger becomes mature.\n\n\u003C!-- marketplace-context:start -->\n## Where this sits\n\nLemma turns Solidity compiler input or Markdown trees into validated, source-linked JSONL chunks with quotation, model, and embedding text kept separate.\n\n**Current frontier.** Callable-surface ABI validation does not independently check return types or state mutability.\n\u003C!-- marketplace-context:end -->\n\nUse Lemma to create chunks. Stop at the JSONL output unless the user separately\nasks for another system to consume it. Berean may use a pinned corpus prepared\nfrom the output, and Ariadne may later bind a release to evidence; Lemma itself\ndoes not embed, index, retrieve, answer, evaluate, or attest.\n\nSynkrisis does not treat Lemma chunks as run observations or compare corpora.\nIts four shipped operations compare validated run observations under a\ndeclared policy; none accepts a Lemma corpus as that subject.\n\n`$SKILL_DIR` is the directory containing this file. Resolve `$PLUGIN_ROOT` as\n`$SKILL_DIR\u002F..\u002F..` and run the bundled commands from there.\n\n## Choose the chunker\n\n- Use `chunkers\u002Fsolidity.py` for one or more solc standard JSON input files.\n- Use `chunkers\u002Fmarkdown.py` for a directory of Markdown documents.\n- If the request is only to inspect or validate an existing JSONL file, read\n  `schema.py` and apply its `Chunk` and `validate()` contract. Do not rerun a\n  chunker without its source input.\n\nRead the target repository's instructions before writing output. Keep generated\nJSONL outside the plugin directory unless the plugin repository itself is the\nnamed target.\n\n## Chunk Solidity\n\nPrefer the included pinned compiler wrapper when Docker or Podman is available:\n\n```bash\ncd \"$PLUGIN_ROOT\"\npython3 chunkers\u002Fsolidity.py \\\n  --input \u002Fabsolute\u002Fpath\u002Fto\u002Fstandard-input.json \\\n  --solc .\u002Fsolc-container \\\n  --include 'src\u002F**' \\\n  --source-ref 'https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo@\u003Ccommit>' \\\n  --out \u002Fabsolute\u002Fpath\u002Fto\u002Fchunks.jsonl\n```\n\nRepeat `--input` to merge compilation units and repeat `--include` for more\nsource patterns. Use `--expect-solc VERSION` when the requested corpus pins a\ncompiler version. Use `--solc solc` only when the user asks for a local compiler\nor the container runtime is unavailable and the local compiler version is\nacceptable.\n\nThe first container run may fetch the pinned image. The compiler process itself\nruns without network access.\n\n## Chunk Markdown\n\nFor a GitBook tree:\n\n```bash\ncd \"$PLUGIN_ROOT\"\npython3 chunkers\u002Fmarkdown.py \\\n  --root \u002Fabsolute\u002Fpath\u002Fto\u002Fdocs \\\n  --summary SUMMARY.md \\\n  --exclude SUMMARY.md \\\n  --source-ref 'https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo@\u003Ccommit>' \\\n  --out \u002Fabsolute\u002Fpath\u002Fto\u002Fchunks.jsonl\n```\n\nPass `--summary ''` when the tree has no GitBook navigation. Add an `--exclude`\nfor every instruction file, generated directory, or unrelated subtree that\nmust not enter the corpus. When a compatible manifest already declares the\nexclusions, pass it with `--manifest` and select its source with `--source`.\n\nMarkdown anchors follow GitBook behavior. Do not claim that they match another\nrenderer without checking that renderer separately.\n\n## Accept the result\n\nBoth chunkers validate before writing. Accept the JSONL only when the command\nexits zero and reports that it wrote the requested file. On failure, report the\nnamed error and do not use an earlier or partial output.\n\nPreserve these distinctions downstream:\n\n- `display_text` holds source text used for quotation;\n- `model_text` holds text prepared for model context;\n- `embed_text` holds text prepared for embedding; and\n- `synthesised: true` means the chunk is assembled and is not a verbatim quote.\n\nRead [`INVARIANTS.md`](..\u002F..\u002FINVARIANTS.md) when changing the chunkers, judging a\nguarantee, or investigating unexpected output. Run the Markdown, Solidity and\nevent test files after any code change.\n\nSolidity event validation runs before chunk construction for every selected\ncontract, abstract contract, interface and library. Compiler `usedEvents` IDs\nresolve across the compilation's ASTs, including excluded dependencies. The\ncheck compares event descriptor counts, names, anonymous flags, ordered\nparameter names and wire types, and every indexed flag with the ABI.\n\nEight exact compiler builds may omit `usedEvents`: `0.6.11+commit.5ef660b1`,\n`0.8.7+commit.e28d00a7`, `0.8.10+commit.fc410830`, `0.8.13+commit.abaa5c0e`,\n`0.8.15+commit.e14f2714`, `0.8.17+commit.8df45f5f`, `0.8.18+commit.87f61d96`\nand `0.8.19+commit.7dd6d404`. Their bare identities and\n`.Emscripten.clang` forms use AST declarations in `linearizedBaseContracts`\norder, keeping the first declaration per external event signature. The\nsignature includes ordered wire types and excludes parameter names, tuple\ncomponent names, indexed flags and anonymous status; those fields remain in\nthe compared descriptor. Unknown or absent identities with missing membership,\nand malformed present `usedEvents` under every identity, refuse. Direct\nvalidation without an explicit version retains that refusal. Build passes its\nsingle observed compiler version to each compilation's validator.\n\nLegacy membership permits at most 100,000 bases or direct declarations per\nlist and 1,000,000 base\u002Fdeclaration visits across selected owners, counting\nrepeated inheritance work. It establishes compiler AST\u002FABI agreement within\nthese pinned builds; it does not claim that emitted library events appear in\nan old owner's ABI or that a compiler's reported identity proves its bytes.\n\nThe resolver accepts elementary types, arrays, nested struct tuples, contract\naddresses, enums, user-defined value types and external function types. Fixed\narray dimensions require matching compiler-resolved AST `typeIdentifier` and\n`typeString` evidence; no ABI field supplies a missing AST type. External\nfunction signatures do not expand into wire tuples, so a signature may refer\nback to its containing struct. Missing, malformed, cyclic or excessive wire\nshapes refuse before delivery. These checks use the existing compiler output\nand establish no deployed-bytecode or runtime-emission claim.\n\n\nSolidity event declarations retain separate owner identities and quotations\nthrough deduplication. Each carries `detail.source_span` with the UTF-8 byte\n`start` and `length` of its complete quotation, including attached NatSpec.\nValidation rejects inconsistent owner\u002Fpath\u002Fsignature\u002FID metadata, missing or\nmalformed spans, repeated spans and duplicate content under one owner. Direct\nschema validation checks those relationships without authenticating unavailable\nsource bytes. An older event corpus without spans must be rebuilt to meet the\ncurrent schema. Non-event and Markdown deduplication keep their existing rules.\n\n## Prepare captured Solidity inputs\n\nUse [captured input preparation](..\u002F..\u002Fdocs\u002Fcaptured-input-preparation.md) when\nan immutable input needs declared metadata extraction, target import closure,\nor a reversible canonical citation map. Run `preparation.py` with a closed\nrequest and a new output directory. Verify its manifest before chunking the\nprepared input; preserve that manifest beside the corpus evidence. Ordinary\nchunking still refuses noncanonical paths.\n\nUse `corpus_evidence.py` to check the registry, private source records, original\nand prepared inputs, compiler transcripts, two output pairs per partition,\nand the independent event census. Its default result covers only declared\npartitions. Require `--complete --full` before claiming full registry coverage.\nMissing original bytes block that transition, and private subjects and source\nnames remain outside public summaries.\n\n## Hand the corpus to Ariadne\n\n`--source-ref` is required whenever `--out` is given. A run without it exits\nnon-zero and writes nothing, because a corpus nobody can trace back to a source\nis the one thing a delivered corpus must not be.\n\nA delivered corpus is two files in one directory: `chunks.jsonl` and the\n`provenance.jsonl` record beside it, which carries the source ref, the digest\nof every input, the selection and the compiler identity. The chunker then\nprints the flags that match what it wrote. Copy them into Ariadne's capture,\nwhich binds that directory into a dataset statement:\n\n```bash\npython3 plugins\u002Fariadne\u002Fscripts\u002Fariadne.py capture-dataset \\\n  --name \u003Ca name for the dataset> \\\n  --first-release-reason \u003Cwhy there is nothing to compare against> \\\n  \u003Cthe flags the chunker printed> \\\n  --out \u002Fabsolute\u002Fpath\u002Fto\u002Fstatement.json\n```\n\nFour flags are the operator's: `--name`, `--out`, and either\n`--first-release-reason` or the `--previous` and `--previous-name` pair that\nnames an earlier release. Everything else was printed, `--release` included, so\ncompose nothing by hand. Those flags describe the corpus as it stood when they\nwere printed, so a capture over a directory whose contents changed in between\nbinds the new bytes. The Markdown chunker records its input paths relative\nto `--root`, so run the capture from there.\n\nLemma writes no statement and signs nothing. It records what produced a corpus\nand stops. Binding those bytes to a release, and attesting to them, belong to\nAriadne, and the record says the source ref was asserted by its caller rather\nthan resolved.\n\n## Promise Machine contract\n\n### lemma-solidity-chunks\n\n- Promise: A successful Solidity chunk run emits schema-valid JSONL whose chunks resolve to the named standard-JSON sources and preserve separate quotation, model and embedding text.\n- Evidence: The exact compiler inputs, selected includes, compiler identity and output, source locations, chunk records and successful built-in validation before write.\n- Evidence classes: checked, recomputed\n- Boundary: The output does not establish source truth, retrieval quality, semantic completeness, independent ABI return or mutability validation, or correctness under another compiler.\n- Authorises: Use of the generated JSONL as source-linked retrieval material for the pinned Solidity compilation inputs.\n- Consequence: 1\n- Refuses: Writing or using partial output after compiler, source-location, schema, include or expected-version failure.\n- Recovery: Correct the pinned input, include set or compiler selection, remove the failed output and rerun the chunker.\n- Exceptions: none\n\n### lemma-markdown-chunks\n\n- Promise: A successful Markdown chunk run emits schema-valid JSONL whose chunks resolve to the selected document tree and preserve source locations, exclusions and synthesised-text labels.\n- Evidence: The exact Markdown tree, navigation or manifest, exclusion set, GitBook anchor method, chunk records and successful built-in validation before write.\n- Evidence classes: checked, recomputed\n- Boundary: The output does not establish document truth, corpus completeness outside the selected tree, compatibility with another renderer, retrieval quality or answer correctness.\n- Authorises: Use of the generated JSONL as source-linked retrieval material for the named Markdown corpus.\n- Consequence: 1\n- Refuses: Including excluded or escaped content, hiding a synthesised chunk as quotation, or using partial output after parsing or validation failure.\n- Recovery: Correct the root, navigation, manifest or exclusions, remove the failed output and rerun the chunker.\n- Exceptions: none\n\n### lemma-corpus-provenance\n\n- Promise: A successful chunk run delivers a corpus of two files whose provenance record binds the asserted source ref, the governed chunker version, the digest of every input, the selection and the compiler identity to a build identifier recomputed from the chunks actually written.\n- Evidence: The provenance record beside the corpus, the source ref as given less any URL userinfo, the digested inputs, the include patterns with the source units present, selected and excluded, the compiler block, and the build identifier recomputed from the delivered file.\n- Evidence classes: checked, recorded, recomputed\n- Boundary: The record does not establish that the ref names a real object, that the ref was clean, that the compiler was honest about its own version, that an ungated compiler was the intended one, or that a citation out of the corpus is faithful.\n- Authorises: Handing the corpus directory to a dataset capture that binds its bytes, and reading the recorded origin, inputs and compiler as what the run was told and observed.\n- Consequence: 1\n- Refuses: Writing a corpus with no recorded origin, recording a value as `unknown`, naming a prefix pin as an exact one, or leaving a record beside chunks it does not describe.\n- Recovery: Supply the missing ref, remove the record the directory already holds or point `--provenance` at it, and rerun the chunker.\n- Exceptions: none\n\n### lemma-chunk-validation\n\n- Promise: A successful direct schema validation establishes that every supplied record satisfies Lemma's `Chunk` shape and field invariants.\n- Evidence: The exact JSONL records, `schema.py` contract, per-record validation and zero validation failures.\n- Evidence classes: checked\n- Boundary: Schema validation does not reproduce chunks without their source input or establish that locations, text and digests match an unavailable corpus.\n- Authorises: Structural inspection or hand-off of the existing JSONL with its source-verification status stated separately.\n- Consequence: 0\n- Refuses: Rechunking without source input or describing schema-valid records as source-verified when their corpus was not checked.\n- Recovery: Obtain the named source input and rerun the appropriate chunker, or report the result as schema-only validation.\n- Exceptions: none\n\n\n### lemma-captured-input-preparation\n\n- Promise: A successful preparation command derives one separate standard-JSON input using only its declared metadata extraction, compiler-resolved target closure or bijective citation mapping, preserving retained source-content bytes and recording the complete reverse map.\n- Evidence: The closed request, original input digest, compiler component pins, bounded compiler transcripts, source maps and selections, replayed preparation manifest, and successful creation of the new output directory.\n- Evidence classes: checked, recorded, recomputed\n- Boundary: This does not establish source truth, compiler honesty, deployed-code identity, operating-system isolation, combined mapping and closure, or corpus conformance. Offline manifest replay checks recorded compiler output without authenticating its producer.\n- Authorises: Chunking the prepared input with its declared selection while retaining the original input and reverse citation map.\n- Consequence: 1\n- Refuses: Unknown or malformed requests, changed pins, ambiguous targets, undeclared metadata, unresolved import edges, nonbijective mappings, changed source content, unmatched selection, or an existing output destination.\n- Recovery: Inspect the stable refusal category, repair the request or restore pinned bytes, and rerun into a new directory; preserve any interrupted directory as incomplete until a valid manifest exists.\n- Exceptions: none\n\n### lemma-corpus-evidence-join\n\n- Promise: A successful corpus evidence check recomputes the declared registry-to-subject-to-source join, original-input custody, preparation manifests, repeat output pairs, independent AST event census and aggregate counts for the exact supplied partitions.\n- Evidence: The pinned registry and full source records, checked subject hashes and memberships, complete input-row denominator, verified bytes for available inputs, preparation transcripts and maps, both corpus\u002Fprovenance pairs, event quotations and recomputed aggregate.\n- Evidence classes: checked, recorded, recomputed\n- Boundary: A sampled check does not establish full coverage; complete custody and full partitions require their explicit flags. Recorded transcripts do not establish compiler execution authenticity, and source-only evidence establishes neither deployed code nor runtime emissions, source truth or acceptance by another task.\n- Authorises: Reporting the checked partition scope and aggregate with missing inputs and source qualifications preserved.\n- Consequence: 1\n- Refuses: Missing, duplicate or extra registry, input or partition rows; changed artifact bytes; inconsistent mappings, transcripts, output pairs, provenance, event census or counts; incomplete custody under --complete; incomplete partitions under --full.\n- Recovery: Restore the exact missing evidence or repair the declared bundle and rerun the same scope; leave dependent full-coverage work blocked while original input bytes are absent.\n- Exceptions: none\n","\u003Cp align=\"center\">\n  \u003Cimg src=\"..\u002F..\u002Fassets\u002Fcharacters\u002Flemma.png\" width=\"1200\">\n\u003C\u002Fp>\n\n# Lemma\n\n## Frontier\n\nLemma owns its own chunking and validation frontier, not Hexaemeron's delivery or\nSolidity frontier. Its version, held target, next job, and maturity\nstate live in [EVOLUTION.md](EVOLUTION.md). Do not recommend or run\nanother frontier pass after that ledger becomes mature.\n\n\u003C!-- marketplace-context:start -->\n## Where this sits\n\nLemma turns Solidity compiler input or Markdown trees into validated, source-linked JSONL chunks with quotation, model, and embedding text kept separate.\n\n**Current frontier.** Callable-surface ABI validation does not independently check return types or state mutability.\n\u003C!-- marketplace-context:end -->\n\nUse Lemma to create chunks. Stop at the JSONL output unless the user separately\nasks for another system to consume it. Berean may use a pinned corpus prepared\nfrom the output, and Ariadne may later bind a release to evidence; Lemma itself\ndoes not embed, index, retrieve, answer, evaluate, or attest.\n\nSynkrisis does not treat Lemma chunks as run observations or compare corpora.\nIts four shipped operations compare validated run observations under a\ndeclared policy; none accepts a Lemma corpus as that subject.\n\n`$SKILL_DIR` is the directory containing this file. Resolve `$PLUGIN_ROOT` as\n`$SKILL_DIR\u002F..\u002F..` and run the bundled commands from there.\n\n## Choose the chunker\n\n- Use `chunkers\u002Fsolidity.py` for one or more solc standard JSON input files.\n- Use `chunkers\u002Fmarkdown.py` for a directory of Markdown documents.\n- If the request is only to inspect or validate an existing JSONL file, read\n  `schema.py` and apply its `Chunk` and `validate()` contract. Do not rerun a\n  chunker without its source input.\n\nRead the target repository's instructions before writing output. Keep generated\nJSONL outside the plugin directory unless the plugin repository itself is the\nnamed target.\n\n## Chunk Solidity\n\nPrefer the included pinned compiler wrapper when Docker or Podman is available:\n\n```bash\ncd \"$PLUGIN_ROOT\"\npython3 chunkers\u002Fsolidity.py \\\n  --input \u002Fabsolute\u002Fpath\u002Fto\u002Fstandard-input.json \\\n  --solc .\u002Fsolc-container \\\n  --include 'src\u002F**' \\\n  --source-ref 'https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo@\u003Ccommit>' \\\n  --out \u002Fabsolute\u002Fpath\u002Fto\u002Fchunks.jsonl\n```\n\nRepeat `--input` to merge compilation units and repeat `--include` for more\nsource patterns. Use `--expect-solc VERSION` when the requested corpus pins a\ncompiler version. Use `--solc solc` only when the user asks for a local compiler\nor the container runtime is unavailable and the local compiler version is\nacceptable.\n\nThe first container run may fetch the pinned image. The compiler process itself\nruns without network access.\n\n## Chunk Markdown\n\nFor a GitBook tree:\n\n```bash\ncd \"$PLUGIN_ROOT\"\npython3 chunkers\u002Fmarkdown.py \\\n  --root \u002Fabsolute\u002Fpath\u002Fto\u002Fdocs \\\n  --summary SUMMARY.md \\\n  --exclude SUMMARY.md \\\n  --source-ref 'https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo@\u003Ccommit>' \\\n  --out \u002Fabsolute\u002Fpath\u002Fto\u002Fchunks.jsonl\n```\n\nPass `--summary ''` when the tree has no GitBook navigation. Add an `--exclude`\nfor every instruction file, generated directory, or unrelated subtree that\nmust not enter the corpus. When a compatible manifest already declares the\nexclusions, pass it with `--manifest` and select its source with `--source`.\n\nMarkdown anchors follow GitBook behavior. Do not claim that they match another\nrenderer without checking that renderer separately.\n\n## Accept the result\n\nBoth chunkers validate before writing. Accept the JSONL only when the command\nexits zero and reports that it wrote the requested file. On failure, report the\nnamed error and do not use an earlier or partial output.\n\nPreserve these distinctions downstream:\n\n- `display_text` holds source text used for quotation;\n- `model_text` holds text prepared for model context;\n- `embed_text` holds text prepared for embedding; and\n- `synthesised: true` means the chunk is assembled and is not a verbatim quote.\n\nRead [`INVARIANTS.md`](..\u002F..\u002FINVARIANTS.md) when changing the chunkers, judging a\nguarantee, or investigating unexpected output. Run the Markdown, Solidity and\nevent test files after any code change.\n\nSolidity event validation runs before chunk construction for every selected\ncontract, abstract contract, interface and library. Compiler `usedEvents` IDs\nresolve across the compilation's ASTs, including excluded dependencies. The\ncheck compares event descriptor counts, names, anonymous flags, ordered\nparameter names and wire types, and every indexed flag with the ABI.\n\nEight exact compiler builds may omit `usedEvents`: `0.6.11+commit.5ef660b1`,\n`0.8.7+commit.e28d00a7`, `0.8.10+commit.fc410830`, `0.8.13+commit.abaa5c0e`,\n`0.8.15+commit.e14f2714`, `0.8.17+commit.8df45f5f`, `0.8.18+commit.87f61d96`\nand `0.8.19+commit.7dd6d404`. Their bare identities and\n`.Emscripten.clang` forms use AST declarations in `linearizedBaseContracts`\norder, keeping the first declaration per external event signature. The\nsignature includes ordered wire types and excludes parameter names, tuple\ncomponent names, indexed flags and anonymous status; those fields remain in\nthe compared descriptor. Unknown or absent identities with missing membership,\nand malformed present `usedEvents` under every identity, refuse. Direct\nvalidation without an explicit version retains that refusal. Build passes its\nsingle observed compiler version to each compilation's validator.\n\nLegacy membership permits at most 100,000 bases or direct declarations per\nlist and 1,000,000 base\u002Fdeclaration visits across selected owners, counting\nrepeated inheritance work. It establishes compiler AST\u002FABI agreement within\nthese pinned builds; it does not claim that emitted library events appear in\nan old owner's ABI or that a compiler's reported identity proves its bytes.\n\nThe resolver accepts elementary types, arrays, nested struct tuples, contract\naddresses, enums, user-defined value types and external function types. Fixed\narray dimensions require matching compiler-resolved AST `typeIdentifier` and\n`typeString` evidence; no ABI field supplies a missing AST type. External\nfunction signatures do not expand into wire tuples, so a signature may refer\nback to its containing struct. Missing, malformed, cyclic or excessive wire\nshapes refuse before delivery. These checks use the existing compiler output\nand establish no deployed-bytecode or runtime-emission claim.\n\n\nSolidity event declarations retain separate owner identities and quotations\nthrough deduplication. Each carries `detail.source_span` with the UTF-8 byte\n`start` and `length` of its complete quotation, including attached NatSpec.\nValidation rejects inconsistent owner\u002Fpath\u002Fsignature\u002FID metadata, missing or\nmalformed spans, repeated spans and duplicate content under one owner. Direct\nschema validation checks those relationships without authenticating unavailable\nsource bytes. An older event corpus without spans must be rebuilt to meet the\ncurrent schema. Non-event and Markdown deduplication keep their existing rules.\n\n## Prepare captured Solidity inputs\n\nUse [captured input preparation](..\u002F..\u002Fdocs\u002Fcaptured-input-preparation.md) when\nan immutable input needs declared metadata extraction, target import closure,\nor a reversible canonical citation map. Run `preparation.py` with a closed\nrequest and a new output directory. Verify its manifest before chunking the\nprepared input; preserve that manifest beside the corpus evidence. Ordinary\nchunking still refuses noncanonical paths.\n\nUse `corpus_evidence.py` to check the registry, private source records, original\nand prepared inputs, compiler transcripts, two output pairs per partition,\nand the independent event census. Its default result covers only declared\npartitions. Require `--complete --full` before claiming full registry coverage.\nMissing original bytes block that transition, and private subjects and source\nnames remain outside public summaries.\n\n## Hand the corpus to Ariadne\n\n`--source-ref` is required whenever `--out` is given. A run without it exits\nnon-zero and writes nothing, because a corpus nobody can trace back to a source\nis the one thing a delivered corpus must not be.\n\nA delivered corpus is two files in one directory: `chunks.jsonl` and the\n`provenance.jsonl` record beside it, which carries the source ref, the digest\nof every input, the selection and the compiler identity. The chunker then\nprints the flags that match what it wrote. Copy them into Ariadne's capture,\nwhich binds that directory into a dataset statement:\n\n```bash\npython3 plugins\u002Fariadne\u002Fscripts\u002Fariadne.py capture-dataset \\\n  --name \u003Ca name for the dataset> \\\n  --first-release-reason \u003Cwhy there is nothing to compare against> \\\n  \u003Cthe flags the chunker printed> \\\n  --out \u002Fabsolute\u002Fpath\u002Fto\u002Fstatement.json\n```\n\nFour flags are the operator's: `--name`, `--out`, and either\n`--first-release-reason` or the `--previous` and `--previous-name` pair that\nnames an earlier release. Everything else was printed, `--release` included, so\ncompose nothing by hand. Those flags describe the corpus as it stood when they\nwere printed, so a capture over a directory whose contents changed in between\nbinds the new bytes. The Markdown chunker records its input paths relative\nto `--root`, so run the capture from there.\n\nLemma writes no statement and signs nothing. It records what produced a corpus\nand stops. Binding those bytes to a release, and attesting to them, belong to\nAriadne, and the record says the source ref was asserted by its caller rather\nthan resolved.\n\n## Promise Machine contract\n\n### lemma-solidity-chunks\n\n- Promise: A successful Solidity chunk run emits schema-valid JSONL whose chunks resolve to the named standard-JSON sources and preserve separate quotation, model and embedding text.\n- Evidence: The exact compiler inputs, selected includes, compiler identity and output, source locations, chunk records and successful built-in validation before write.\n- Evidence classes: checked, recomputed\n- Boundary: The output does not establish source truth, retrieval quality, semantic completeness, independent ABI return or mutability validation, or correctness under another compiler.\n- Authorises: Use of the generated JSONL as source-linked retrieval material for the pinned Solidity compilation inputs.\n- Consequence: 1\n- Refuses: Writing or using partial output after compiler, source-location, schema, include or expected-version failure.\n- Recovery: Correct the pinned input, include set or compiler selection, remove the failed output and rerun the chunker.\n- Exceptions: none\n\n### lemma-markdown-chunks\n\n- Promise: A successful Markdown chunk run emits schema-valid JSONL whose chunks resolve to the selected document tree and preserve source locations, exclusions and synthesised-text labels.\n- Evidence: The exact Markdown tree, navigation or manifest, exclusion set, GitBook anchor method, chunk records and successful built-in validation before write.\n- Evidence classes: checked, recomputed\n- Boundary: The output does not establish document truth, corpus completeness outside the selected tree, compatibility with another renderer, retrieval quality or answer correctness.\n- Authorises: Use of the generated JSONL as source-linked retrieval material for the named Markdown corpus.\n- Consequence: 1\n- Refuses: Including excluded or escaped content, hiding a synthesised chunk as quotation, or using partial output after parsing or validation failure.\n- Recovery: Correct the root, navigation, manifest or exclusions, remove the failed output and rerun the chunker.\n- Exceptions: none\n\n### lemma-corpus-provenance\n\n- Promise: A successful chunk run delivers a corpus of two files whose provenance record binds the asserted source ref, the governed chunker version, the digest of every input, the selection and the compiler identity to a build identifier recomputed from the chunks actually written.\n- Evidence: The provenance record beside the corpus, the source ref as given less any URL userinfo, the digested inputs, the include patterns with the source units present, selected and excluded, the compiler block, and the build identifier recomputed from the delivered file.\n- Evidence classes: checked, recorded, recomputed\n- Boundary: The record does not establish that the ref names a real object, that the ref was clean, that the compiler was honest about its own version, that an ungated compiler was the intended one, or that a citation out of the corpus is faithful.\n- Authorises: Handing the corpus directory to a dataset capture that binds its bytes, and reading the recorded origin, inputs and compiler as what the run was told and observed.\n- Consequence: 1\n- Refuses: Writing a corpus with no recorded origin, recording a value as `unknown`, naming a prefix pin as an exact one, or leaving a record beside chunks it does not describe.\n- Recovery: Supply the missing ref, remove the record the directory already holds or point `--provenance` at it, and rerun the chunker.\n- Exceptions: none\n\n### lemma-chunk-validation\n\n- Promise: A successful direct schema validation establishes that every supplied record satisfies Lemma's `Chunk` shape and field invariants.\n- Evidence: The exact JSONL records, `schema.py` contract, per-record validation and zero validation failures.\n- Evidence classes: checked\n- Boundary: Schema validation does not reproduce chunks without their source input or establish that locations, text and digests match an unavailable corpus.\n- Authorises: Structural inspection or hand-off of the existing JSONL with its source-verification status stated separately.\n- Consequence: 0\n- Refuses: Rechunking without source input or describing schema-valid records as source-verified when their corpus was not checked.\n- Recovery: Obtain the named source input and rerun the appropriate chunker, or report the result as schema-only validation.\n- Exceptions: none\n\n\n### lemma-captured-input-preparation\n\n- Promise: A successful preparation command derives one separate standard-JSON input using only its declared metadata extraction, compiler-resolved target closure or bijective citation mapping, preserving retained source-content bytes and recording the complete reverse map.\n- Evidence: The closed request, original input digest, compiler component pins, bounded compiler transcripts, source maps and selections, replayed preparation manifest, and successful creation of the new output directory.\n- Evidence classes: checked, recorded, recomputed\n- Boundary: This does not establish source truth, compiler honesty, deployed-code identity, operating-system isolation, combined mapping and closure, or corpus conformance. Offline manifest replay checks recorded compiler output without authenticating its producer.\n- Authorises: Chunking the prepared input with its declared selection while retaining the original input and reverse citation map.\n- Consequence: 1\n- Refuses: Unknown or malformed requests, changed pins, ambiguous targets, undeclared metadata, unresolved import edges, nonbijective mappings, changed source content, unmatched selection, or an existing output destination.\n- Recovery: Inspect the stable refusal category, repair the request or restore pinned bytes, and rerun into a new directory; preserve any interrupted directory as incomplete until a valid manifest exists.\n- Exceptions: none\n\n### lemma-corpus-evidence-join\n\n- Promise: A successful corpus evidence check recomputes the declared registry-to-subject-to-source join, original-input custody, preparation manifests, repeat output pairs, independent AST event census and aggregate counts for the exact supplied partitions.\n- Evidence: The pinned registry and full source records, checked subject hashes and memberships, complete input-row denominator, verified bytes for available inputs, preparation transcripts and maps, both corpus\u002Fprovenance pairs, event quotations and recomputed aggregate.\n- Evidence classes: checked, recorded, recomputed\n- Boundary: A sampled check does not establish full coverage; complete custody and full partitions require their explicit flags. Recorded transcripts do not establish compiler execution authenticity, and source-only evidence establishes neither deployed code nor runtime emissions, source truth or acceptance by another task.\n- Authorises: Reporting the checked partition scope and aggregate with missing inputs and source qualifications preserved.\n- Consequence: 1\n- Refuses: Missing, duplicate or extra registry, input or partition rows; changed artifact bytes; inconsistent mappings, transcripts, output pairs, provenance, event census or counts; incomplete custody under --complete; incomplete partitions under --full.\n- Recovery: Restore the exact missing evidence or repair the declared bundle and rerun the same scope; leave dependent full-coverage work blocked while original input bytes are absent.\n- Exceptions: none\n",{"name":5,"metadata":24,"description":7},{"version":25},"0.5.1","main","6b6406ecd922c4127bc688e0b5122bbe395be0eb","plugins\u002Flemma\u002Fskills\u002Flemma",6,"https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills","https:\u002F\u002Fgithub.com\u002Fwildcat-finance","https:\u002F\u002Fwildcat.finance","Banking, But Worse","2026-11-07 17:14:07",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add wildcat-finance\u002Fskills --skill lemma",{"tool":41,"command":42},"bunx","bunx skills add wildcat-finance\u002Fskills --skill lemma",{"tool":44,"command":45},"pnpm","pnpm dlx skills add wildcat-finance\u002Fskills --skill lemma","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Flemma\u002Fskills\u002Flemma\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"DEMONSTRATION.md","REFERENCE","参考文档",2253,"https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Flemma\u002Fskills\u002Flemma\u002FDEMONSTRATION.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"EVOLUTION.md",4017,"https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Flemma\u002Fskills\u002Flemma\u002FEVOLUTION.md",[60,67,73,80,86,92],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7APAWXHFSKVQEJBAHKASH25","example","A deliberately unsupported evidence class fixture.","https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fpromise-machine\u002Funsupported-evidence-class\u002Fplugins\u002Fexample\u002Fskills\u002Fexample\u002FSKILL.md",[],[],{"skillNo":68,"name":62,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7APATBK93107VF5NMPA3RJH","A router fixture target.","https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fpromise-machine\u002Funresolved-router\u002Fplugins\u002Fexample\u002Fskills\u002Fexample\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7APARV9C0MQB8WTB0GGAAMG","promise-machine","A deliberately unresolved router.","https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fpromise-machine\u002Funresolved-router\u002F.agents\u002Fskills\u002Fpromise-machine\u002FSKILL.md",[],[],{"skillNo":81,"name":62,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7APAQMDG4977HXGSKMB29KV","A deliberately unclassified skill fixture.","https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fpromise-machine\u002Funclassified-skill\u002Fplugins\u002Fexample\u002Fskills\u002Fexample\u002FSKILL.md",[],[],{"skillNo":87,"name":62,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7APAPE6DE05A24J4BYPK6WY","A deliberately unattributed exception fixture.","https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fpromise-machine\u002Funattributed-exception\u002Fplugins\u002Fexample\u002Fskills\u002Fexample\u002FSKILL.md",[],[],{"skillNo":93,"name":62,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7APAKYXRTABBSN7Q637CC6M","A deliberately conflated version fixture.","https:\u002F\u002Fgithub.com\u002Fwildcat-finance\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fpromise-machine\u002Fpackage-as-skill-version\u002Fplugins\u002Fexample\u002Fskills\u002Fexample\u002FSKILL.md",[],[]]