ADR-035 + ADR-036: ψ-chain Term variants + ResolverTuple substrate parameter
ADR-035 + ADR-036 land together — the doc explicitly says they're
co-dependent, so I'm committing both in one commit. ADR-035 introduces
nine ψ-chain Term variants (Nerve, ChainComplex, HomologyGroups, Betti,
CochainComplex, CohomologyGroups, PostnikovTower, HomotopyGroups,
KInvariants); ADR-036 introduces the R: ResolverTuple substrate parameter
that carries application-provided resolver instances for the eight
resolver-bound ψ-Term variants (Betti is resolver-free pure computation).
The Term enum extends from twelve variants to twenty-one. The model
declaration's parameter shape extends from <H, B, A> to <H, B, A, R>.
Closure-body grammar extends from G1-G20 to G1-G29.
ADR-035 commits the ontology-defined ψ-pipeline ψ_1..ψ_9 (per
spec/src/namespaces/op.rs and spec/src/namespaces/homology.rs in the
UOR-Foundation/UOR-Framework ontology) as substrate Term variants.
The ψ-chain is the structural-witness arm of op:InferenceOperation
(ι = P ∘ Π ∘ G); together with the ψ-pipeline's resolution arm flowing
through combinatorial Term variants, the catamorphism evaluates the
complete typed-iso surface end-to-end. Verb bodies witness per-value
structural admission relationships (admission as a homology property
of the value's CONSTRAINTS-induced structure rather than a runtime
predicate) directly through prism vocabulary; the framework's
verifiability commitment per ADR-001 + ADR-019 (canonical computational
equivalences as homology classes) is realized at the closure-body
grammar layer. Brute-force Term::FirstAdmit enumeration retires from
verb bodies whose admission relationships have a structural-witness
expression.
ADR-036 commits the ResolverTuple substrate parameter paralleling
AxisTuple per ADR-030 — same tuple-of-bounded-types pattern, same
dispatch through associated constants — but carries per-value content
provision rather than per-domain operation kernels. Foundation declares
ResolverTuple, ResolverCategory enum, eight resolver traits
(NerveResolver<H>, ChainComplexResolver<H>, HomologyGroupResolver<H>,
CochainComplexResolver<H>, CohomologyGroupResolver<H>, PostnikovResolver<H>,
HomotopyGroupResolver<H>, KInvariantResolver<H>), eight Has<Cat>Resolver<H>
marker traits, MAX_RESOLVER_TUPLE_ARITY const, eight Null* resolver
baselines, and a NullResolverTuple. The SDK provides the resolver! macro
paralleling axis!. Standard library sub-crates may contribute resolver
baselines paralleling axis baselines per ADR-031. Application authors
declare resolver impls in resolver! struct fields (eight foundation-
fixed canonical field names: nerve, chain_complex, homology_groups,
cochain_complex, cohomology_groups, postnikov, homotopy_groups,
k_invariants); the SDK proc-macro infers Has<Cat>Resolver<H> bounds in
the model declaration's where-clause from verb bodies' ψ-Term emissions.
Foundation's pipeline::run_route signature extends to thread the
ResolverTuple alongside the AxisTuple.
Block A (both ADRs inserted at end-of-file in 09_architecture_decisions.adoc).
Block B cross-references in ADR-013 Consequences (extended with both ADRs);
ADR-022 D4 trait body comment (now mentions all four substrate parameters);
ADR-022 D5 run_route signature (extended with R: ResolverTuple);
ADR-026 G12 disambiguation paragraph (reserved-identifier set extended with
nine ψ-chain identifiers); TR-12 (same extension); ADR-029 fold-rules (nine
new ψ-Term fold-rules added) + per-variant preamble (now names four substrate
parameters) + variant-count statement (twelfth → twenty-first); ADR-030
Consequences (ResolverTuple parallel to AxisTuple); ADR-031 Consequences
(resolver baselines parallel to axis baselines).
Block C: Section 4 strategic-decision row added; Section 8 Closure Across
Layers paragraphs appended (one for ADR-035, one for ADR-036).
Block D glossary: nine ψ-Term variant entries; nine grammar-form entries
(G21-G29); ResolverTuple + ResolverCategory + MAX_RESOLVER_TUPLE_ARITY +
resolver! + ψ-chain resolver traits cluster + Has<Category>Resolver<H>
marker-trait entry.
Audit-pass for variant-count + grammar-count consistency: ADR-020 Decision
Term-enum enumeration (twelve → twenty-one); ADR-033 Consequences (twelve →
twenty-one); Section 5 BBV vocabulary re-exports row (twelve → twenty-one
plus G1-G20 → G1-G29); Section 8 Concepts initial-algebra paragraph (twelve
→ twenty-one) + PrismModel concept entry; glossary prism_model! entry
(G1-G20 → G1-G29 + extended reserved-identifier set + run_route signature
with R: ResolverTuple).
Domain-neutralization: per the cleanup commit 3a65899, the wiki is
domain-neutral. The ADR-035/036 source documents had stray "Bitcoin
mining" / "Sha256dHasher" / "PrismBtcNerveResolver" references; these
have been generalized in the inserted text (e.g., "Bitcoin mining model's
NerveResolver" → "admission-by-homology application's NerveResolver";
"Sha256dHasher" → "MyHashAxisImpl"). The architectural commitment is
domain-agnostic; concrete examples in ADRs use generic placeholder names.
Encoding: the source documents had mangled UTF-8 (Ï for ψ, ι for ι, β
for β, etc.); these have been translated to proper Unicode Greek/math
characters in the inserted text.
Forward-references: the ADR-035 ↔ ADR-036 cross-references resolve
internally (both ADRs land in this commit). Foundation/SDK/standard-
library reconciliation is the next step: foundation extends the Term
enum with the nine ψ-Term variants, declares the ResolverTuple trait
family, extends pipeline::run_route's signature; SDK provides the
resolver! proc-macro; the standard library contributes resolver
baselines.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>