← Vaquill AI Primary LawCONTENT HISTORY

Update to Vaquill AI Primary Law

Snapshot Nov 7, 2026 · 06:14 UTC · version 1.0.4

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Vaquill AI Primary Law and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Trace the chain between a statute and the regulations that implement it, in either direction. Subject: <citation or act_id>.",
  "included_files": [],
  "name": "authority",
  "skill_md_contents": "---\nname: authority\ndescription: Trace the chain between a statute and the regulations that implement it, in either direction. Subject: <citation or act_id>.\n---\n\nTrace the authority chain for whichever subject the conversation is about. If it is not clear from the conversation, ask for it before calling anything.\n\nStatutes grant power; regulations exercise it. This command walks the link, which is a different question from \"what does this say\".\n\n1. Resolve the input to an `act_id` if it is a citation string.\n2. Fetch the section and read the link fields.\n\n## The fields, and which direction each points\n\n| Field | On | Points to |\n| --- | --- | --- |\n| `implementingRegulations` | USC | The CFR parts issued under this statute |\n| `statutoryAuthority` | CFR | The statute granting the rulemaking power |\n| `lawImplemented` | CFR and some state regs | The statute the rule actually **implements** |\n\n**`statutoryAuthority` and `lawImplemented` are not the same thing**, and conflating them is the mistake this command exists to prevent. One is the power to write the rule, the other is the substantive law being carried out. Florida populates both and they routinely differ.\n\n## Then widen with the citation graph\n\n- `crossReferencesUsc` and `crossReferencesCfr` are the outbound references in the text. `'self:<section>'` denotes another section of the same title.\n- `relatedCitations` carries outbound references that are neither USC nor CFR. On several corpora `crossReferencesUsc`/`Cfr` are 0% populated, so this is the only outbound set they have.\n- `get_section_cited_by` (2 credits) is the **inbound** direction: which sections point at this one. USC and CFR only; state codes and Federal Register rules carry no cross-reference index and return empty with a `note`, refunded.\n\n## Two honesty constraints\n\n**Inbound citations are evidence, not proof.** A citation the publisher never recorded in machine-readable form cannot appear. `total` is the size of the returned list capped by `limit`, not a corpus-wide count; `truncated` says more exist.\n\n**A chain is not an argument.** That a regulation was issued under a statute says nothing about whether it is valid, current, or applies to the user's facts. Report the links, not a conclusion about authority.\n\n## For federal statutes, consider the enacting text too\n\n`publicLawCites` on a USC section carries structured Statutes at Large citations, each with `statVolume`, `statPage` and a `display` string. Those resolve into `corpusType: \"SESSION_LAW\"`, which holds federal law **as enacted** rather than as codified.\n\nWorth fetching when the question turns on what Congress actually passed rather than how it was compiled. Note that acts before 1957 carry no public law number and are cited by chapter.\n\n## Report\n\nDraw the chain as a short list, statute at the top, regulations beneath, with the field that established each link named. Where a link is absent, say the corpus records none rather than implying no such relationship exists.\n"
}

SHA-256 of public snapshot: 941182464d347b5c050754876837e67bdb7bbbf97b4e62cee6b40f4c704bda35