Repository navigation
Description
Context
TAXONOMY.md reserves case-style precedential_weight values for judicial authority and requires not-applicable for statutes, licenses, guidance, and other non-case sources. Eight non-case cards currently violate that rule:
- AUTH-0070, AUTH-0071, AUTH-0090
- AUTH-0093
- AUTH-0110, AUTH-0111, AUTH-0112, AUTH-0113
They encode binding or nonprecedential in the same field used to rank cases. This can make a retriever collapse operative statutes/rules, binding case precedent, and nonbinding technical guidance into one hierarchy. The correction must not imply that statutes or federal rules lack legal force.
Proposal
Set case-style precedential weight to not-applicable for the affected non-case cards. Preserve the source's legal or practical force in a separate controlled field, such as legal_effect or authority_role, and enforce a type/weight invariant. Keep settlement treatment as an explicitly documented exception if none-settlement remains useful.
Acceptance criteria
- Every statute, license, administrative material, and official-guidance card uses
precedential_weight: not-applicableunless the taxonomy documents a narrow exception. - The eight identified cards are corrected without weakening prose about operative federal statutes or rules.
- A separate controlled field distinguishes operative law, court rule, official guidance, license text, and technical standard where needed.
- A validator rejects non-case cards carrying
binding,persuasive-*,nonprecedential,default-only, ornone-allegation. - Settlement cards either retain
none-settlementunder an express exception or migrate to the new authority-role field consistently. - Retrieval tests rank statutes/rules, case precedent, license text, and guidance without treating them as the same concept.
Decisions
- Confirmed taxonomy contradiction, P1 metadata integrity. This is a classification correction, not a legal-force conclusion.
- Separate force from precedent.
precedential_weightalone cannot describe every authority type safely. - No LICENSE edit or merits change. Existing substantive analysis remains pending attorney review.
Open questions
- What controlled values should
legal_effectorauthority_rolepermit? - Is
none-settlementbest retained as a documented exception or moved out of precedential weight entirely?
Activity
zackees commentedon Aug 25, 2026
Sol adversarial review - 2026-08-25
Verdict: confirmed, with an exact-count correction and narrower invariants; leave open. The repository has a real internal contradiction.
TAXONOMY.mdassignsnot-applicableto statutes, licenses, guidance, and other non-case authorities, and the authority template says every non-case authority must use it for both posture and weight. The eight listed cards violate that rule. The metadata defect is demonstrated; the claimed retrieval harm remains prospective because this repository has no checked-in corpus retriever or validator.Reproducible census
At current
maincommit40ee7108f4b46b6b8fb1976f5c8b3cd996bdfb42, scanning the YAML frontmatter of every file matching^id: AUTH-gives 102 cards: 60 case and 42 non-case. Non-case types are 30license, 1license-condition, 1license-draft, 5statute, 3administrative-material, 1official-guidance, and 1settlement.That final command returns nine, not eight:
AUTH-0070,AUTH-0071,AUTH-0090,AUTH-0110:statute/binding.AUTH-0093,AUTH-0111,AUTH-0112:administrative-material/binding.AUTH-0113:official-guidance/nonprecedential.AUTH-0008:settlement/none-settlement, and it also uses case posturesettled.Thus eight is exact only for the issue's proposed rejected-value set after treating settlement as an exception. Under the taxonomy and template as currently written,
AUTH-0008is a ninth type/weight violation and the sole non-case posture violation. The other 33 non-case cards already usenot-applicable. No case card usesnot-applicablefor posture or weight.The eight named cards are genuinely non-case source cards.
AUTH-0093,AUTH-0111, andAUTH-0112are judicially promulgated federal rules, but they are not adjudicative opinions, holdings, or case precedent. Calling themadministrative-materialexposes a missingcourt-ruletype; it does not makeprecedential_weight: bindingcoherent. Federal rules have the force and effect of law under the Rules Enabling Act process (U.S. Courts; 28 U.S.C. § 2072).AUTH-0113is an official NIST technical report aimed at evidence-management professionals, not an adjudication or evidence rule (NIST publication record). Setting case precedent tonot-applicablemust therefore be paired with positive effect/role metadata so retrieval does not demote statutes or court rules below merely persuasive cases.Corrections and taxonomy loopholes
statute+none-settlement, an unknown value, or a future non-case type omitted from the checklist. Use closed enums plus an allowed type/posture/weight matrix. The first acceptance criterion also omits current taxonomy typesregulation,license-condition,license-draft,settlement, andsecondary-source.authority_type != case => procedural_posture == not-applicable && precedential_weight == not-applicable. If the corpus later admits agency adjudications, add a distinctadministrative-decisiontype and consciously decide whether this field covers administrative precedent; do not silently exempt alladministrative-material.court-rule(and likelytechnical-standard) rather than relying on prose to say anadministrative-materialis legally operative.regulation, agency guidance, agency adjudication, and an agency technical report have materially different roles.judicial-decision,party-filing,docket-record,statute,regulation,court-rule,license-instrument,settlement-instrument,settlement-report,official-guidance,technical-standard, andsecondary-analysis. Candidate effects includegenerally-operative,case-specific-order,party-agreement,conditional-private-instrument,nonbinding-guidance, andinformational-only, always qualified by jurisdiction/parties/effective date. These are design candidates for counsel, not legal conclusions.AUTH-0008relies on a secondary announcement, sosettlement-reportplus informational/reported effect is safer than implying authenticated party-binding terms. By contrast, acasecard whose litigation ended in settlement can coherently retainprocedural_posture: settledandprecedential_weight: none-settlement; the current case examples areAUTH-0039,AUTH-0043,AUTH-0044, andAUTH-0046.casebucket and weight enum cannot express all three safely. Coordinate the source-artifact model with retrieval: make authority proposition treatment machine-checkable #24 rather than creating divergent parsers.legal_effectinto a universal ranking score. Operative text, forum-specific case precedent, private license terms, reported settlements, and technical practice answer different questions. Retrieval should filter by actor, proposition, forum, artifact role, effect scope, status/date, posture, and source quality before applying any ranking.Stronger acceptance criteria
procedural_posture, allowedprecedential_weight, source/artifact role, legal-effect category, and required scope/status fields.precedential_weight: not-applicable; classifyAUTH-0093,AUTH-0111, andAUTH-0112as court rules rather than generic administrative material; preserve prose and structured metadata stating their operative federal procedural/evidentiary effect.AUTH-0008explicitly. Recommended default:not-applicableposture/weight plussettlement-reportrole. Keepnone-settlementonly forcaserecords whose disposition is settlement, unless counsel approves a documented alternative.non-adjudicative => posture/weight exactly not-applicable; enforce the converse for adjudicative records; reject unknown values, omitted current/future types, and exception values on the wrong type.tools/license_headers.py,tests/test_license_headers.py, andheader-policy.schema.jsonvalidate source-license headers only; no current code consumes authority frontmatter.Questions for attorney review
precedential_weightlimited to judicial decisions, or should a separately typed agency adjudication use it within the agency/target forum?court-rulewithgenerally-operativeeffect, and what jurisdiction/effective-date fields are mandatory?generally-operative,case-specific-order,party-agreement,conditional-private-instrument,nonbinding-guidance, andinformational-onlyacceptable effect categories, or should force and role remain separate axes?History, duplicate, and resolution check
The taxonomy, template invariant, and eight named violations were introduced together in PR #18 / commit
40ee710;AUTH-0008originated in PR #16 and received its conflicting structured values in the same PR #18 commit. Current localHEAD,origin/main, remoteHEAD, andmainall resolve to40ee710. GitHub has no later open or merged PR implementing this issue and no duplicate issue. #19 is the parent; #24 is complementary proposition/artifact work, not a duplicate. Before this review, #27 had no comments or resolving timeline event. Closure would therefore be unsupported.This is a corpus-integrity assessment for attorney review, not legal advice, a license decision, or a change to
LICENSE.