Generated from
cat-harness/skills/library/library-core/adopt-methodology-from-source.md— do not edit here.
Adopt a methodology from a source document
The adoption rules are methodology-adoption. This skill is the operating order for applying them when somebody shares a document and asks for its method to be used. The owner, 2026-09-23: “update ‘methodology source/paper’ process to describe general process of what you are doing”.
Worked case: WireGen (arXiv:2312.07755) became methodologies/wiregen. Issue #1023.
Steps (one per process activity)
- Origin and licence. Record the authors, venue, identifier, and the licence the source itself states.
- No stated licence means reference only: the library entry holds headings, page ranges and a summary in our own words.
- A source with no origin is a house process. Write a skill instead of a methodology.
- Ingest (
Process_Ingestion,library-ingestion) — the basic flow: the source is accepted, its metadata goes into the KG, and it is catalogued inlibrary/. Reading a document into sections is a content-type refinement above this layer (placement PR6), and it keeps the rules that applied here: choose the rung mechanically, and never accept an inferred chapter tree. - Related work (
Process_RelatedWork,related-work-coordination). Search beans (beans list --json,beans query) and the repository’s issues and open PRs for work the method touches.- Categorize each hit: overlaps, coordinate; affected by; out of scope; or unrelated. Give each a one-line summary.
- Judgement decides the categories. Present them with context, options and a recommendation (
interaction-modality§4.1), and ask whether and how to coordinate. Do not act before the answer. - This is the same step CRDM runs when a requirement starts or changes in chat.
- Render the method faithfully: what the source says, section by section, then a table of what is adopted and what is refused, each with its reason.
- Extensions beyond the source are marked as ours.
- Reported results are not imported as facts.
- Place it by ownership (
methodology-adoption§4), and declare the directory. - Integrate by calling, not copying. The method’s judgement points are call activities into existing processes:
Process_Adjudication,Process_OptionsAnalysis,Process_Ingestion. A change an existing process needs is made there, or becomes a bean against it. - Tools. Every script, CLI or checker the process relies on gets a Tool node (
cat-harness/tools/index.ts) satisfying a named skill.check:toolsgates it. - Owner review. The owner adopts it, sends it back for changes (to step 4), or declines. A decline is recorded with its reason.
Refusals
- Never hold a source’s bytes or text when its licence does not allow it.
- Never adopt a method by naming it.
- Never coordinate with related work without asking.
Processes that run this skill
| process | step(s) that name it |
|---|---|
| Adopt a methodology from a source document | Establish origin and licence; Integrate: call existing processes; Every skill and tool used becomes a Tool |