Registers of Claim

On this page

Summary

The Standing Framework classifies claims on three independent axes: layer, support, and provenance. Layer identifies the work a claim performs in the theory; support identifies what warrants it; provenance identifies how it entered the corpus. The axes are kept separate because a reconstruction is not thereby a derivation, an operational rule is not thereby optional, and an application can contain claims at several strengths. Where a page lists several values on one axis, the list is an unordered inventory of positions present on that page, not a priority ranking or a claim that every value applies to every conclusion; local prose assigns the values to subclaims.

Registers describe warrant and dependency; they do not certify truth. Page-level dependencies supply an acyclic reading-order projection, while typed relations among contracted stable claims record exact premises, bridge premises, application inputs, and refusal effects where the projection would lose material structure. Neither representation claims to inventory every local subclaim. Refusal traces what survives when a reader declines a refusable premise. Defeat shows that a claim is false, invalid, contradictory, misclassified, or unfaithfully reconstructed and therefore requires revision rather than treatment as a reader's optional exit.

This page is an orientation and inventory page rather than a doctrinal module. It defines the register vocabulary, explains how pages display dependencies, and distinguishes refusal from evidence or argument that defeats a claim.

Layer

Conceptual core

The source framework's foundation and fixed conceptual relations: someone, standing, demands and exercises, answerability against authorization, the settlement prohibition, and the account. The core identifies the parties and relations the rest of the theory uses; it does not by itself produce a complete roster of claims or a method for resolving conflicts.

Diagnostic theory

The account of what is owed, what wrongs, and what cannot justify itself to its target. It includes claim grounds, the holder's good, authority across time, adequate justification, possession, and constraint. Diagnostic claims may be reconstructed, generalized, clarified, derived, defended, proposed, open, or empirical; membership in the layer does not settle support.

Operational system

The architecture for acting when claims interact: the six-stage pipeline, comparison, risk, necessity, exit, residue, enforcement, and institutional decision. Much of this layer is proposed rather than derived. Refusing one of its rules removes the capacity that rule supplied; it does not leave the same verdict in place by a weaker route.

Application

A domain-specific use of the earlier layers. Applications inherit only the premises they state. They do not acquire the support status of a layer as a whole, and a defended application does not weaken the premises it validly uses.

Orientation

Indexes, intellectual context, practical orientation, rival views, and editorial maps. These pages help readers locate claims without giving the orientation itself doctrinal authority.

The layers are load-ordered, not ranked by importance. The conceptual core can remain while a diagnostic interpretation is refused; diagnostic verdicts can remain while an operational proposal is refused; an application fails only where one of its actual dependencies fails.

Navigation groups are separate from these layers. They place pages in a usable reading sequence, including orientation pages, rival views, and practical-orientation material, without assigning those pages a theory position.

Support

Foundational

A commitment the framework presents but does not derive. The directed form is a leading instance: that an obligation can be owed to a holder at all, rather than merely be an obligation concerning them. A foundational label locates where derivation stops. It neither supplies affirmative warrant nor immunizes the commitment from refusal, counterargument, or defeat.

Derived

A conclusion that follows from stated premises and inferences. Every indispensable premise, including bridge premises, must be visible. A conclusion can be derived given a defended or proposed premise; the inference is valid without promoting the premise, and refusing the premise removes the conditional conclusion. The party floor has this form: it follows from the directed relation together with defended non-derivative welfare relevance and bearer-sufficiency, while none of those premises is promoted by the derivation.

Defended

A substantive position argued for but not entailed by the accepted foundations and derivations. Defended claims are refusable at the cost stated on their pages.

Proposed

Architecture or completion offered because the prior theory needs a rule, distinction, or procedure that it did not already contain. A proposal may be well supported and still remain a proposal. Refusing it restores the earlier gap.

Optional

A module not adopted by the canonical theory but specified as a coherent amendment. Optional differs from proposed: a proposal belongs to the canonical construction while remaining refusable; an optional module is an alternative the construction declines unless expressly adopted.

Open

A question the framework does not resolve, together with the premise, evidence, or conceptual work a resolution would require. The inventory is at Open Questions.

Empirical

A claim whose truth depends on evidence rather than the framework's conceptual machinery. Empirical support can be necessary to an application without becoming philosophical doctrine.

Provenance

Source framework

Source framework marks material developed by Nume before the present reconstruction.

Reconstruction

Reconstruction organizes or interprets that material without claiming that the organization was already explicit.

Generalization

Generalization extends a source claim beyond its original domain.

Clarification

Clarification resolves an ambiguity or supplies explicit content to an inherited formula.

Completion

Completion adds machinery where the inherited framework stopped.

Application provenance

Application carries prior machinery into a domain.

Rival

Rival presents a position the framework does not adopt.

Personal orientation

Personal orientation records Nume's own refusable practice or stance.

Editorial

Editorial marks navigation, history, or corpus administration.

Provenance is not ownership by itself. A reconstructed or completed claim can still belong to the current Standing Framework; the label records its route into the theory so that a reader can refuse the addition without pretending it was present from the beginning.

How pages expose position

Concept and doctrine pages state their axes in a fixed order:

Theory position: diagnostic theory · defended · generalization.

They then name a coarse page-level dependency projection:

Page-level dependencies: Standing · Authorization.

Composite pages may name more than one support or provenance value, then classify important subclaims where they occur. Values within an axis form an unordered page-level inventory; their display order carries no priority, and only local prose determines which value governs a particular claim. These entries are rendered from the page manifest. The dependency list means that the page uses the cited module somewhere in its argument and supplies an acyclic order for retrieval; it is not an assertion that every conclusion on the page depends on every cited page.

Where that projection hides a material relation, the theory contract names the stable consumer and source claims directly. It distinguishes a premise from a bridge premise and from an application input whose refusal requires revision without making the consumer wholly derivative. Strict refusal effects propagate through those contracted claim relations. The graph is opt-in: a claim not entered there remains governed by its definition-site prose, and absence of an edge does not establish independence.

Orientation and inventory pages deliberately omit these lines where they classify or route other pages rather than advance doctrine. Rival-view and practical-orientation pages may likewise omit them where their role is to present a position outside the framework's dependency structure. Absence of metadata is intentional only for those roles; it must not be read as an unstated layer, support level, or provenance.

Refusal and exit

Rejecting non-derivative welfare relevance or the bearer-sufficiency bridge removes the derived party floor and every conclusion that strictly depends on it. Welfare-bearing subjectivity, subject separateness, and the directed form survive; refusing only welfare-relevance's minimum sufficiency condition can also leave non-derivative reason-giving intact, while bearer-sufficiency refusal leaves voluntary and other independently grounded claims available.
Rejecting the directed relation removes the directed-obligation form itself: "must answer to" dissolves into mere affectedness or collapses into an authorization requirement. Bearer-sufficiency becomes inapplicable and the party floor falls. Welfare-bearing subjectivity, subject separateness, non-derivative welfare relevance, holder-neutral addressee relations, impersonal appraisal and party-relative assessment, and authorization as a distinct grantor relation survive.
Rejecting a derived premise or inference removes every conclusion that actually depends on it.
Rejecting a defended claim leaves independent core and derived material standing, but removes conclusions derived only given that claim.
Rejecting a proposal returns the problem to the point at which the proposal supplied missing architecture.
Rejecting an optional module leaves the canonical theory unchanged.
An open or empirical classification identifies work or evidence still needed; it is not a request to assent.

Refusal propagates through the actual claim relation, not by page proximity, the coarse page projection, or rhetorical centrality. Points of Entry gives the complementary map of where readers may arrive.

Refusal is not defeat

Refusal records a disagreement while leaving the refused claim represented as the framework actually holds it. A reader can reject a defended premise, decline a proposal, or adopt an optional alternative; the dependency graph then shows the cost without declaring the premise false.

Defeat instead identifies a defect in the corpus or its support. A counterexample can defeat a universal claim; evidence can falsify an empirical classification; an inference can fail or conceal an indispensable bridge; two retained commitments can contradict; a reconstruction can misstate its source; or a register can claim more or less support than the argument supplies. These findings require correction at the definition site and propagation through dependencies, applications, summaries, and metadata. They may not be converted into another refusal row merely to preserve the existing text.

A surprising or unwelcome verdict is not by itself a defeat, just as an intuitive convergence is not confirmation. Either can identify where to test the premises. The register system supplies no commitment that ethical theories are only navigated rather than assessed for truth, coherence, evidence, and validity; it records the support and consequences needed to conduct that assessment without hiding disagreement.

Limits

The classification is corrigible. A critic may show that a claimed derivation hides a bridge premise, that a proposed rule follows from accepted premises, or that a reconstruction changes rather than recovers the source.
Page-level labels and dependencies are summaries. Where a page contains claims at different positions, local labels, typed contracted relations, and definition-site prose govern.
Accurate registers do not prevent prose from producing the felt force of a stronger claim. Persuasion Without Capture treats the force of presentation as an answerability problem rather than a metadata problem alone.

What refusal changes

The rules above are enough to interpret a page's register. Each contracted claim carries its own refusal record — what refusing it costs, what no longer follows, and what survives — rendered on the page that defines it and addressable by the claim's own permalink. The index below lists every claim by layer and links to those per-page cards. Pure derivations fall through refusal of their premises rather than receiving independent exits, and the record certifies no premise as true.

The refusal explorer reads the same records for a chosen set of premises at once rather than one at a time, and keeps the selection in its address, so a particular position can be linked to.

Every contracted claim

93 claims, 78 of them refusable, grouped by the layer of the page that defines each. Follow a claim to its per-page card for its dependencies and refusal record.

no declared layer

Completeness module — optional, refusable