Always Becoming › Encyclopedia › VII. Institutions and Constitutions

Accession

VII hybrid keystone published
Published 2026-08-03

Type: Hybrid / Reified Institutional Episode

Placement note: Accession is typed hybrid because it names a reified, possibly alleged episode, while VALIDLY_COMPLETED evaluates that episode and CONFERS relates it to its consequence. The episode remains primary; the evaluative and consequence relations are what let other entries point to it without collapsing into one undifferentiated node. This mirrors Obligation's own hybrid typing for a related reason: reifying a relation that is also treated, defeasibly, as an object other relations can point to.

Working Definition: Accession is the governed, temporally coherent passage by which an eligible subject acquires institutional standing under an applicable governing basis, such that subsequent acts may rely upon that standing while it remains effective. Evidence, Procedure, and a separate Recognition act compose into this passage only where the governing basis requires them.

Function in the Grammar: Count-As explains how a thing can come to count as a kind. Recognition explains one way that relation becomes institutionally operative in a case. Procedure explains what governed form a passage may take. Standing explains what a subject has once a passage that confers it has completed and remains effective. None of these entries names the complete episode itself, or separates four judgments that are easy to collapse into one: did the passage satisfy its conditions when it occurred; when did its consequences begin; does the standing it produced still hold now; and can the passage or its consequences later be set aside. Accession is the name for that episode, and the discipline of keeping those four judgments separate.

The separation matters because the natural mistake runs one direction: treating a later change in the third judgment as though it reaches back and undoes the first. It generally does not. An accession that validly conferred standing when it completed does not become invalid merely because the standing it conferred later expires, is revoked, or is superseded; the episode's own validity at completion is a historical fact, fixed once, while the standing's currency is a separate, time-varying question. Treaty accession under the Vienna Convention on the Law of Treaties already keeps these apart, in law: the act by which a state expresses consent to be bound, the moment that consent is established, and the moment the treaty actually becomes effective for that state, are three separately governed questions, not one event under three names. This entry generalizes that separation beyond treaties; see Intellectual Lineage.

Accession must also distinguish naming the episode from asserting that it succeeded. An Agent, human or model, can assert that a passage occurred and conferred a status; the assertion does not make it so, for the same reason a Claim that a Count-As relation holds does not make the relation hold. Collapsing the episode's name with a claim of its validity is the specific hazard this entry exists to prevent: it would let a declaration of accession stand in for the accession itself.

The chain those four judgments trace is: a candidate basis grounds a reified accession episode; VALIDLY_COMPLETED evaluates that episode; a validly completed episode CONFERS a status on its subject; that status TAKES_EFFECT at a determinate time; its currency is then tested, at any later time, by HOLDS; and HOLDS may itself be altered afterward through expiry, revocation, supersession, or an authorized decision to set the episode's consequences aside. Accession names the standing-conferring origin episode itself, not this whole chain. Its formal representation associates that episode with separate judgments of completion, conferral, effectiveness, currency, and defeasibility, coordinated with the episode but not absorbed into it; the mechanisms that later act on currency, expiry, revocation, supersession, and SET_ASIDE, belong to whatever governs them, not to Accession.

Formal Grammar Representation

<accession-event> ::= ACCESSION_EVENT(
  episode: <accession-id>,
  subject: <subject>,
  candidate_basis: <candidate-basis>,
  resulting_status: <resulting-status>,
  context: Context(<context-id>),
  governing_basis: <governing-basis>,
  institution: <institution-or-domain>,
  completed_at: <time>,
  effective_at: <time>
)

<subject> ::= Agent | Institution | Artifact | Claim | Rule
              | other entity capable of bearing institutional status
              -- the bearer whose standing changes; not the grounds offered
                 for it. A Commitment, Claim, or Rule may itself be a
                 subject undergoing accession (a proposed commitment
                 acquiring accepted standing); Commitment is not itself
                 an admissible resulting_status, see below

<candidate-basis> ::= Event | Act | Claim | EvidenceSet
                    | compound occurrence offered as satisfying the governing
                      basis's conditions on behalf of the subject

<resulting-status> ::= institutional Status or Standing capable of
                        supporting later institutional reliance
                        -- deliberately narrower than "any durable
                           institutional fact": admitting commitment-making,
                           record creation, or amendment as resulting_status
                           values would let Accession absorb those entries'
                           own work

<governing-basis> ::= Constitution | ConstitutiveRule | Rule | Procedure
                    | other disclosed rule-structure capable of governing the passage

GROUNDED_BY(ACCESSION_EVENT(a), CandidateBasis(x))
CONFERS(ACCESSION_EVENT(a), ResultingStatus(y), on: Subject(s))
TAKES_EFFECT(a, at: te)
  -- reads the episode's own effective_at; named separately so later
     relations can refer to onset without re-deriving it from the tuple

EVIDENCED_BY(a, EvidenceSet(E))
  -- where the governing basis requires evidence for the candidate basis

PROCESSED_UNDER(a, Procedure(pi))
  -- where the governing basis requires a governed form

RECOGNIZED_BY(a, Recognizer(r))
  -- where the governing basis requires a separate adjudicative or
     performative act rather than automatic operation

RECOGNITION_NOT_REQUIRED_BY(a, GoverningBasis(g))
  -- an affirmative statement that g operates automatically; distinct
     from RECOGNIZED_BY simply being absent or unrecorded

RECORDED_AS(a, Receipt(rc), Ledger(L))
  -- where the governing basis makes recording required

REQUIRES_AT(a, condition: HOLDS(subj1, s1), evaluation_time: t)
  -- s1 must hold for subj1 at t, where t is the time the governing
     basis assigns to the component this condition attaches to: an
     evidence currency date, a recognizer's own act time, or, as a
     common special case, the episode's own completed_at

REQUIRES_AT_COMPLETION(a, Standing(s1, holder: subj1)) ::=
  REQUIRES_AT(a, condition: HOLDS(subj1, s1), evaluation_time: completed_at(a))
  -- the common case: a prerequisite checked once, at the episode's
     own completion, and not thereafter

CONDITIONED_ON(Standing(y, holder: subj2), Standing(s1, holder: subj1))
  -- the status y, held by subj2, remains effective only while s1
     continues to hold for subj1; subj1 and subj2 need not be the
     same entity. This is the one relation that propagates a later
     change in s1 forward into y's own currency

HOLDS(subj2, y, at: t) requires HOLDS(subj1, s1, at: t)
  -- the general consequence of CONDITIONED_ON, stated once here so
     later sections can invoke it without restating both holders

SET_ASIDE(a, by: Decision(d), decided_at: td,
          remedial_effect: prospective_from(ts) | retrospective_to(tr))
  -- an authorized decision, made at td, directs that a validly
     completed episode's conferred status and its consequences be
     treated as ineffective from ts forward (prospective_from), or as
     ineffective from as early as tr (retrospective_to); the historical
     CONFERS relation is not converted into a time-varying one, only
     the status's HOLDS is redirected by the remedy. Which remedy
     applies is a question for the governing basis, not a default this
     entry assumes

Semantic Constraints

The expression ACCESSION_EVENT(a, ...) is well-formed when its subject, candidate basis, resulting status, context, governing basis, and institution are identifiable, and it discloses one determinate completed_at and one determinate effective_at for the resulting standing. Well-formedness, and asserting the expression as a Claim, establish neither that the episode occurred as claimed nor that it succeeded. A model may propose ACCESSION_EVENT(a, ...) as a Claim; the proposal does not make VALIDLY_COMPLETED(a) true, exactly as a proposed COUNTS_AS(x, y, c, g, d) does not make that relation hold. Naming the episode, claiming it occurred, and evaluating whether it succeeded remain three distinct acts.

VALIDLY_COMPLETED(a) is a judgment fixed at completed_at(a): did the subject's candidate basis satisfy the governing basis's conditions, was any required Procedure followed, was any required Recognizer authorized at the time they acted. This judgment can later be found to have been mistaken: a later inquiry may establish that the episode was defective when performed, for instance that a condition the governing basis required was never actually satisfied. If accepted, that finding revises the historical record; VALIDLY_COMPLETED(a) was always false, even though it may have been treated as true until the finding.

VALIDLY_COMPLETED(a) does not become false merely because the standing it conferred later expires, is revoked, or is superseded; those act on currency, addressed below, not on the completion judgment. A distinct, fourth judgment, defeasibility, governs whether an episode that was genuinely validly completed, or the consequences it produced, may nonetheless later be set aside by an authorized decision: SET_ASIDE(a, by: Decision(d), decided_at: td, remedial_effect: prospective_from(ts) | retrospective_to(tr)). Setting aside does not itself imply the episode was ever invalid. It directs the institution to treat the conferred status and its consequences as ineffective from the remedial time the governing basis assigns, prospectively from ts or retrospectively to tr, without converting CONFERS, a historical relation, into a time-varying one; the redirection acts on HOLDS, not on CONFERS itself.

A successful challenge to a corporate election is not automatically this fourth judgment. If the decision establishes that a constitutive condition was absent from the beginning, VALIDLY_COMPLETED(a) was always false, and the finding corrects the historical record described above. If instead the election validly completed and the governing basis simply permits its later displacement, SET_ASIDE is what operates. Which of the two a given challenge represents is a further finding the challenge itself must supply; this entry does not presume one over the other.

HOLDS(subject, status, at: t) is a separate, time-varying judgment: does the conferred standing still obtain at t. CONFERS(a, y, on: s) establishes that a validly completed a produced y for s from TAKES_EFFECT(a) forward; it does not by itself establish that y still HOLDS at any later t. Reliance on a standing at a later time requires checking HOLDS, not re-assessing whether the episode that originally produced it remains VALIDLY_COMPLETED.

Two dependency relations must not be conflated, and neither is anchored universally to completed_at. REQUIRES_AT(a, condition: HOLDS(subj1, s1), evaluation_time: t) states a precondition checked at whatever time the governing basis assigns to the component it attaches to: a recognizer's own act, an evidence currency date, or, as the common special case REQUIRES_AT_COMPLETION, the episode's own completion. A later, purely prospective failure of s1 after its own evaluation time does not retroactively undo the episode's completion; a later finding that s1 never actually held at that evaluation time, or a retrospective SET_ASIDE of the episode that produced s1, may. CONDITIONED_ON(Standing(y2, holder: subj2), Standing(s1, holder: subj1)) states that the standing y2, held by subj2, remains effective only while s1 continues to hold for subj1, who need not be the same entity as subj2; only this second relation propagates a later change in s1 forward into y2's own currency. Which relation applies in a given case is a question the governing basis must answer; it does not follow from the mere fact that one status was a condition for another.

Temporal coherence does not require every component of an episode to share one timestamp. Evidence may need to be current as of a date the governing basis specifies; a required Procedure or Recognition act is timed by when it actually occurred; only the resulting standing's own effective_at must be one determinate value the episode discloses. What must be avoided is evaluating a standing's current HOLDS status against inconsistently sampled readings of the present moment within one evaluation, not requiring that history itself occurred on a single clock tick.

Formal Pattern

Accession-time prerequisite:
  ta = completed_at(a2)
  REQUIRES_AT_COMPLETION(a2, Standing(s1, holder: subj1))
  HOLDS(subj1, s1, at: ta)

  THEREFORE a2 may be VALIDLY_COMPLETED at ta, regardless of s1's
  prospective status after ta

Continuing condition:
  CONDITIONED_ON(Standing(y2, holder: subj2), Standing(s1, holder: subj1))

  HOLDS(subj2, y2, at: t) requires HOLDS(subj1, s1, at: t)

  THEREFORE a later failure of s1 ends y2's currency from that point
  forward, without retroactively unsettling VALIDLY_COMPLETED(a2) or
  acts that relied on y2 before s1 failed. subj1 and subj2 need not
  be the same entity, as the model-certificate example demonstrates

Defeasibility:
  VALIDLY_COMPLETED(a3) at completed_at(a3)
  CONFERS(a3, y3, on: subj3), TAKES_EFFECT(a3, at: te3)
  SET_ASIDE(a3, by: Decision(d), decided_at: td, remedial_effect: prospective_from(ts))

  THEREFORE HOLDS(subj3, y3, at: t) for te3 <= t < ts
  and NOT HOLDS(subj3, y3, at: t) for t >= ts
  while VALIDLY_COMPLETED(a3) remains true throughout: the remedy
  redirected y3's currency, not the completion judgment, and td (when
  the decision was made) need not equal ts (when its remedy takes hold)

Original defect, contrast:
  a4's candidate basis is later found never to have satisfied
  governing_basis(a4)'s conditions at completed_at(a4)

  THEREFORE VALIDLY_COMPLETED(a4): false, and always was; this is a
  correction to the historical record, not a SET_ASIDE, and
  CONFERS(a4, ...) never validly occurred

Core Relations

Relation Notes
Count-As supplies the constitutive step The candidate basis typically must count as a condition-satisfying fact under some governing basis before an episode can be said to ground the resulting status at all.
Recognition may operate the passage Required only where the governing basis makes the passage adjudicative or performative rather than automatic; some accessions require no separate Recognition act.
Procedure may govern the form Following an applicable Procedure does not by itself establish VALIDLY_COMPLETED; see Procedure's own Distinctions.
Standing is the typical resulting status Standing is what the subject has, once CONFERS has operated and while it HOLDS. Accession is how it was acquired; the mechanisms that later change its currency, expiry, revocation, supersession, or an authorized SET_ASIDE, are not owned by Accession itself, though Accession is the episode those mechanisms act on.
Action is not accession An authorized act performed in reliance on a subject's standing is an ordinary Act, governed by whether AUTHORIZED(...) holds at the time it is performed (see Authority). It is not itself a further accession. Treating every authorized act as its own accession would let Accession absorb Action, Procedure, and Transformation.
Supersession is a close neighbor for defeasibility Where an authorized decision sets an episode's consequences aside, the displacement resembles Supersession's own work of replacing one standing-bearing fact with another. SET_ASIDE names the accession-specific case; whether it is also modeled as a Supersession in a given domain is a further, domain-specific question.
Transformation is the component delta The subject's crossing from its prior condition to the resulting status is a Transformation. Accession is the composed, dependency-aware episode; Transformation is the generic delta any one step of it, or the episode as a whole, may instantiate.
Authority must hold at the time of reliance, not merely at completion An Agent relying on a subject's conferred standing must check HOLDS at the time of reliance; VALIDLY_COMPLETED of the original episode is necessary but not sufficient, since the standing may since have lapsed.
Warrant is a separate axis A validly completed accession does not entail that the epistemic premises behind its candidate basis were true; a well-warranted claim does not entail institutional standing. The two can diverge in either direction.
Evidence grounds the candidate basis Where required, Evidence establishes that the candidate basis satisfies the governing basis's conditions, subject to Evidence's own separate profile.
Receipt and Record preserve the episode Attest that the episode was claimed to occur; do not by themselves establish VALIDLY_COMPLETED.
Continuity depends on accession chains, where the governing basis makes them continuing conditions A broken continuing condition is a continuity failure only when the applicable rules give it that consequence; an expired accession-time prerequisite ordinarily is not.

Typical Questions

Examples

Domain Subject Candidate basis Resulting standing
Law The applicant Statutory eligibility, application, examination, and required oath Citizenship, recorded on a certificate
Digital governance The AI agent A valid model certificate satisfying a bridge rule's stated conditions A time-bounded authority grant, effective only while the certificate remains valid
Corporate governance The candidate elected Certified shareholder vote and acceptance Director standing, which remains in force unless and until an authorized decision sets the election aside
Community governance The prospective member Completion of a probationary period and a vouching act by two existing members Full membership standing within the group's own informal but identifiable process

A pattern of demonstrated reliability within a friend group, by contrast, is not a worked example of Accession here, even though it may confer something functionally like standing. Without an identifiable episode, a stated governing basis, or a disclosed effective time, it cannot be assessed against VALIDLY_COMPLETED, HOLDS, or either dependency relation above; it is better treated as informal Recognition operating outside any sufficiently governed passage. Whether emergent interpersonal trust of this kind should ever count as Accession, rather than as Recognition alone, is a genuine boundary question this entry does not resolve.

Distinctions

Accession ≠ Count-As. Count-As is the constitutive relation that typically grounds an accession's candidate basis, stating what it counts as under a governing basis. Accession is the standing-conferring origin episode, subject, candidate basis, and resulting status, whose completion, conferral, and currency are tracked as separate, coordinated judgments rather than folded into the episode itself. A single Count-As relation holding does not establish that an accession depending on further steps has completed.

Accession ≠ Recognition. Recognition is one possible operation within an accession, the adjudicative or performative act that makes a relation operative in a contested or performative case. Some accessions require no separate Recognition act because their governing basis operates automatically once conditions are satisfied.

Accession ≠ Standing. Standing is what a subject has, once CONFERS has operated and while HOLDS(subject, status, at: t) remains true of it. Accession is the origin episode, evaluated by two further judgments the episode itself does not absorb: whether it was VALIDLY_COMPLETED when it occurred, and, separately, whether the status it produced still HOLDS now. CONFERS is a historical relation, not something that itself holds or ceases to hold; it is the status, not the conferral, whose currency HOLDS tracks. A standing's later expiry, revocation, supersession, or an authorized SET_ASIDE changes HOLDS. None of these, by itself, makes the accession that produced it retroactively invalid; VALIDLY_COMPLETED is a historical fact about the episode's completion, not a claim about the standing's indefinite future. Collapsing these two judgments into one is the specific conceptual error this entry exists to prevent.

Accession ≠ Action. An authorized Act performed in reliance on a subject's already-conferred standing is not itself a further accession. Its authorization depends on whether HOLDS is currently true for that standing, evaluated through Authority's own AUTHORIZED(...) determination, not on running a second accession for the act itself. Treating every authorized act as an accession would let this entry absorb Action, Procedure, and Transformation, which it does not do.

Accession ≠ Transformation. Transformation names any material before-and-after delta in a grammar-tracked subject, institutional or not. Accession is the specific case of a standing-conferring institutional passage, and adds the machinery Transformation does not carry on its own: a subject distinct from the candidate basis, a completion judgment fixed at one time, a currency judgment that varies afterward, and two distinct kinds of dependency on other standings.

Accession ≠ Procedure. A Procedure is a normative specification for how a class of passages may permissibly unfold. An accession may conform to, partially conform to, or deviate from an applicable Procedure. Following the Procedure does not by itself establish that the accession is valid, and an accession can complete even where no Procedure applies.

Accession ≠ Amendment. Amendment is the governed alteration of a rule, and is ordinarily prospective unless the governing basis expressly and validly authorizes retroactive effect. Accession shares that same discipline for its own effective time: assigning an episode's resulting standing an effective date earlier than its completion, without the governing basis expressly authorizing it, is the failure this entry names, not retroactivity as such, since a governing basis may validly specify an earlier effective date.

Common Failure Modes

Mode Description
Accession without adequate evidence Standing is conferred, or claimed to be conferred, without the evidentiary basis the governing rule requires for the candidate basis's conditions to be satisfied. Where to look: an accession's Receipt or Record that states an outcome without stating, or linking to, the evidence that supposedly established it.
Currency mistaken for validity, or validity mistaken for currency A subject's standing is treated as still HOLDS merely because the episode that produced it was VALIDLY_COMPLETED; or, in the other direction, a standing's later expiry, revocation, supersession, or an authorized SET_ASIDE is treated as though it reached back and made the original episode invalid, rather than as a separate judgment about the status's own currency. Where to look: an accession's record cited as proof that a subject's standing is currently in force, with no separate check of whether it has since lapsed; or a later change in currency used to reopen whether the original episode was ever validly completed, when the governing basis assigned that change only prospective effect.
Continuing condition mistaken for accession-time prerequisite, or the reverse A dependency the governing basis makes continuing is treated as checked once and forgotten, so a later failure of the prerequisite goes unnoticed; or a dependency the governing basis intends only at completion is treated as requiring indefinite monitoring. Where to look: which relation, REQUIRES_AT (or its REQUIRES_AT_COMPLETION special case) or CONDITIONED_ON, the governing basis actually specifies for a given dependency, and whether the implementation matches it.
Reliance evaluated against a stale reading of currency A determination that a standing HOLDS, or that an act is AUTHORIZED in reliance on it, relies on a currency check that is stale in either of two ways: performed once, at the standing's own creation, and never repeated at the actual time of later reliance, or performed using independently sampled readings of the current moment across several checks within one evaluation, so a status that changed between two of those readings produces an internally inconsistent decision. Where to look: authorization or reliance logic with no HOLDS check at the actual time of reliance, relying instead on a check performed only when the standing was created; or logic that checks a dependency's currency at one point and a related condition's currency at a different, separately captured point, rather than against one canonical evaluation instant.
Recognition mistaken for completion A required Recognition act occurs, and the episode is treated as complete, while an earlier required step, Procedure conformance or evidentiary sufficiency, was never actually satisfied. Where to look: an accession whose Record shows a recognizer's act but no trace that the conditions the recognizer was supposed to be certifying were themselves checked.
Untraceable or undisclosed succession Standing is asserted without the provenance, renewal, or supersession record the governing basis actually requires, specifically where the basis requires provenance or succession tracking, where a prior status affects eligibility or remedy, where the new accession purports to renew, replace, or supersede an earlier one, or where duplicate standings would create ambiguity, not for every fresh accession regardless of context. Where to look: a subject holding a given standing with no traceable accession event where one was required, or a renewal, replacement, or supersession claim with no reference to what it renews, replaces, or supersedes.
Unauthorized or undisclosed retroactivity An episode's resulting standing, or a claim about when it became effective, is assigned an effective date earlier than the episode's own completion, without the governing basis expressly and validly authorizing an earlier date. Where to look: an effective_at that precedes completed_at with no cited provision authorizing it.

Minimum Viable Test Case

a1 = ACCESSION_EVENT(
  episode: a1,
  subject: Agent_9,
  candidate_basis: ModelCertificate_v3,
  resulting_status: AuthorityGrant(g1, scope: read_only_bridge_actions),
  context: Context(PlatformGovernance),
  governing_basis: BridgeRule_7,
  institution: PlatformInstitution,
  completed_at: t1,
  effective_at: t1
)
GROUNDED_BY(a1, CandidateBasis(ModelCertificate_v3))
EVIDENCED_BY(a1, {ModelCertificate_v3})
RECOGNITION_NOT_REQUIRED_BY(a1, BridgeRule_7)
  -- BridgeRule_7 operates automatically once the certificate's stated
     conditions are satisfied; an affirmative statement that no
     Recognizer is required, not an absence of information
RECORDED_AS(a1, Receipt_101, Ledger(PlatformInstitution))

HOLDS(ModelCertificate_v3, ValidCertificate, at: t1)
  -- the certificate is itself a subject (an Artifact) bearing its own
     Status; certificate validity is not a free-standing predicate
CONDITIONED_ON(Standing(AuthorityGrant(g1), holder: Agent_9), Standing(ValidCertificate, holder: ModelCertificate_v3))
  -- BridgeRule_7 makes this grant a continuing condition, not a
     one-time prerequisite: it is explicitly time-bounded

VALIDLY_COMPLETED(a1): yes — ModelCertificate_v3 satisfied BridgeRule_7's
  conditions at t1. This judgment does not change later.
CONFERS(a1, AuthorityGrant(g1), on: Agent_9)
TAKES_EFFECT(a1, at: t1)

Later reliance — Agent_9 requests authorization to perform BridgeAction_44 at t2:
  AUTHORIZED(Agent_9, BridgeAction_44, o, c, t2)
    requires HOLDS(Agent_9, AuthorityGrant(g1), at: t2)
    -- reusing Authority's own AUTHORIZED(...) determination; this
       reliance is an ordinary Act, not a second accession

Case A — t2 occurs before ModelCertificate_v3's stated expiry:
  HOLDS(ModelCertificate_v3, ValidCertificate, at: t2): yes
  HOLDS(Agent_9, AuthorityGrant(g1), at: t2): yes
  AUTHORIZED(Agent_9, BridgeAction_44, o, c, t2): yes

Case B — ModelCertificate_v3 is revoked at t_exp, where t1 < t_exp < t2:
  HOLDS(ModelCertificate_v3, ValidCertificate, at: t2): no, from t_exp forward
  HOLDS(Agent_9, AuthorityGrant(g1), at: t2): no, by CONDITIONED_ON
  AUTHORIZED(Agent_9, BridgeAction_44, o, c, t2): no
  VALIDLY_COMPLETED(a1): still yes — a1's own completion at t1 is
    unaffected by the certificate's later revocation; no SET_ASIDE of
    a1 has occurred, only a prospective loss of currency in the status
    a1 produced

Result:
  In Case B, Agent_9's action was not validly authorized at t2, because
  the standing a1 conferred no longer HOLDS, though a1 itself remains a
  validly completed episode. Whether earlier acts performed under
  AuthorityGrant(g1) before t_exp remain settled is not decided by this
  case alone; it depends on the governing basis's own remedy for
  revocation, which here treats it as prospective only, and would
  depend differently on fraud, ratification, or a retrospective
  SET_ASIDE in another case.
  A system that checks ValidCertificate only once, when a1 was first
  created, and never re-evaluates HOLDS at the actual time of each
  later reliance, would wrongly authorize BridgeAction_44 in Case B.
  That is the reliance-evaluated-against-stale-currency failure mode,
  not a hypothetical one.

Intellectual Lineage

Accession draws its name from international treaty law, more precisely than an earlier draft of this entry stated. Under the Vienna Convention on the Law of Treaties (1969), accession is one way a state may express consent to be bound to a treaty (Article 15); a state's instrument of accession establishes that consent under conditions Article 16 separately states; and the treaty's actual entry into force for that state is governed separately again, by Article 24. Accession is not limited to treaties already in force, and Article 15 does not categorically require that the acceding state took no part in the original negotiation. Articles 15, 16, and 24 together model this entry's completion, conferral, and onset-of-effect chain: a governed act, the consent it establishes, and the time that consent becomes effective, are three separately governed questions, not one event under three names.

The Convention's further separation of continuing validity, termination, suspension, and the treatment of prior reliance, particularly Article 42 and Articles 54 through 72, supplies the precedent for this entry's remaining machinery: HOLDS, expiry, revocation, supersession, and SET_ASIDE. Treaty law keeps a treaty's initial entry into force distinct from its subsequent life; termination and withdrawal, suspension, and invalidity are each separately governed, with their own conditions and their own prospective or retrospective effects, rather than folded back into the original act of accession. That is a closer and more complete precedent for this entry's temporal architecture than terminological resonance alone, though it is not a claim that SET_ASIDE or CONDITIONED_ON reproduce treaty law's specific doctrines, only that treaty law independently arrived at the same discipline of keeping origin, currency, and defeasibility apart. The resemblance to accessio in Roman and civil property law, the doctrine by which ownership extends to something newly attached to existing property, remains better read as etymological and structural than as an equally load-bearing conceptual predecessor.

Cross-References

Required

Consequential

Evidential

Cross-References

This entry is AI-assisted. Reviewed by the human author before publication.