Part A - Identify the Work and the Organizational Condition
ADM.1 - Frame the Administrative Condition Needed for the Work
Type: Architectural
Status: Stable
ADM.1:0 - Use this when
Use this pattern when an administrative request is hard to interpret, several providers call their part “done”, or one word such as “trip” hides different results. Begin with the participant’s intended work and the condition the administration is expected to supply.
The pattern governs the relation between the work intended and its needed administrative condition. Its first result is a bounded enabling question: what condition is needed, for whom, from whom and by when. This lets the handler select the relevant service instruction or return a business question to whoever is responsible for that work.
If those facts are already clear and an adequate instruction covers the request, apply that instruction.
ADM.1:1 - Problem frame
A participant asks for travel, access, reimbursement, an appointment or another administrative result because it makes some work possible. The request may name a form or portal operation instead of the needed condition: “close the ticket”, “create an account”, or “approve the trip”. A local provider can perform that operation while the participant still cannot do the intended work.
The relevant participants may belong to different units or organizations. A research group requests access, an archive owner decides eligibility, and a technical provider provisions a credential. The administrative question connects their contributions to the needed condition across those unit or organizational boundaries.
ADM.1:2 - Problem
How can a handler establish what administration is expected to supply, and recognize its completion, without confusing that result with the outcome of the work it enables?
A vague completion label has practical costs. It can send a failed negotiation to a travel desk, close an unusable access request, or make a service owner claim that administrative success guarantees a business outcome.
ADM.1:3 - Forces
The handler needs enough context to identify the real result, but asking for the whole business plan can delay a simple service. Providers need precise boundaries for their commitments, while the participant needs a condition that works across those boundaries. An early answer should enable action, yet a superficially complete record can hide a missing permission or a failed provision.
These pressures favour a small explicit question. Expand it only where a missing distinction could change the provider, the applicable rule, the expected result or the next action.
ADM.1:4 - Solution
ADM.1:4.1 - Recover the needed condition from the request
Identify the participant’s intended work and the condition needed for it from the request or existing account. Resolve unclear points from the available evidence or ask the participant when their contribution is needed. “I need to examine the archive before the experiment” is more useful than beginning with the account-creation form.
Then name the condition that would make the administrative part usable. For archive work this may be permitted read access for the named researcher during the necessary interval. For a journey it may be authorized travel with usable transport and accommodation. Include conditions that determine whether or how the recipient can use the service.
Distinguish the condition from its usual evidence. A booking confirmation supports a claim about accommodation; establish that the accommodation is usable for the traveller when the claim concerns provision. Once the authorized decision maker approves the stated journey and expenditure under the travel rule, that authorization is established. The providers still have to supply usable transport and accommodation.
ADM.1:4.2 - Separate the subjects hidden by the label
For each completion or failure statement, ask what happened to what. “The trip succeeded” could concern the journey, the negotiating work, the administrative case or the records supporting expense settlement. State the relevant subject and its result before combining the statements.
Use a short comparison when several meanings are active. Different subjects may have an enabling relation, a contribution relation or some other connection. Determine that connection from the actual work. If the statements instead concern one event from different participants’ positions, use ADM.4 to preserve their correct correspondence.
When an operations account is genuinely unclear about cases, work, resources or descriptions, OPS.3 supplies those distinctions. When the answer depends on how several structures relate, use C.32.MWA. A routine enabling question does not require either inquiry to be repeated.
ADM.1:4.3 - Bound the administrative promise
Name the participant who needs the condition, the provider or providers expected to supply it, the relevant time and the supplied conditions for its use. Recover the applicable authority or eligibility through ADM.2 only when it is unresolved. Use ADM.3 when timing or change affects the answer.
Write a first result in ordinary language, for example:
The archive service needs to provide Mara with usable, permitted read access to collection R by 25 September so that she can prepare experiment E. The archive owner decides eligibility; the access provider supplies the technical means. The experiment’s outcome remains with the research team.
That statement is sufficient to locate the next service or eligibility question. It need not become a new form. If the provider is unknown, identify the missing responsibility and, when known, the service owner able to establish it.
ADM.1:4.4 - Choose the next action and stop
When the requested condition, recipient, provider and needed time are identified, and the applicable service instruction’s prerequisites for the next handling action are established, the handler uses that instruction to obtain or verify provision. Reuse adequate supplied facts and decisions. If a required fact or decision is unresolved, identify the missing contribution. Use available evidence to settle a factual question or direct it to the appropriate source. Obtain decisions from the holder of the relevant authority.
For a missing administrative condition, state what the participant still cannot use and why the local “done” evidence is insufficient. For a failed business result after the administrative condition was supplied, return the next business decision to whoever has responsibility for the business work. An administrative provider can still examine its own contribution if new evidence connects it to that failure.
Framing finishes when its recipient can use the statement of the needed condition or the identified gap. Completion of the enabled work is a separate question.
ADM.1:4.5 - What changes in practice
The request becomes about a usable condition and a responsible next action. The handler can distinguish an incomplete service from an unsuccessful business task, and providers can see which joins matter to the participant’s use. An already adequate request proceeds directly.
ADM.1:5 - Archetypal Grounding
ADM.1:5.1 - A completed journey and an unsuccessful negotiation
In this constructed case, an employee travels to negotiate a supply agreement. The supplied travel rule requires an eligible traveller, authorized expenditure, usable transport and accommodation, and settlement of the required expenses. Those conditions are satisfied. The parties nevertheless fail to reach the intended agreement.
| Subject | Stipulated result | Next action |
|---|---|---|
| Journey and stay | The employee travelled and used the accommodation. | Retain the relevant provision evidence for its intended administrative use. |
| Negotiating work | The parties reached no agreement. | The person responsible for the negotiating work decides whether to revise the offer, continue negotiations or stop. |
| Administrative handling | The stated travel conditions and required expense settlement were satisfied. | The handler may report that administrative result complete under the supplied rule. |
Report the completed travel service and the failed negotiation separately. The negotiating decision returns to the party responsible for the agreement. If the accommodation had been unusable and the employee had arranged a replacement personally, the administrative account would instead retain that failure and the displaced effort even if the negotiations later succeeded.
ADM.1:5.2 - An ordinary request that needs no reframing
A requester identifies the eligible traveller, destination, permitted dates and existing booking instruction. The provider and completion condition are clear. The handler uses that instruction. Asking for another description of the organizational architecture would add effort without changing the next action.
ADM.1:6 - Bias-Annotation
An internal service view can privilege the provider’s queue over the participant’s actual work. Use evidence from the receiving work, including the participant’s account when needed. Include a supported failed or abandoned request when it changes the service account. The business owner can also misattribute every failed outcome to administration; keep the claimed causal contribution separate from the observed service failure.
A participant may be unable to disclose the full business purpose. Request only enough permitted context to determine the needed condition and applicable rule.
ADM.1:7 - Conformance Checklist
For the actual enabling question, examine whether:
- The participant’s intended work and the administrative condition are identifiable in ordinary language.
- Each completion or failure claim refers to the relevant subject.
- The recipient, provider, needed time and conditions on which the requested use depends are supplied or named as unresolved.
- Evidence such as an approval or provider message is interpreted against the promised condition.
- An adequate ordinary request can proceed. Any remaining fact can be investigated locally or requested from a competent source. A missing decision goes to its holder, or the result identifies the missing responsibility.
These questions assess the framing. Whether the service was actually supplied requires evidence of that result under its applicable conditions.
ADM.1:8 - Common Anti-Patterns and How to Avoid Them
Closing the form while the condition is absent. An account-creation ticket says “done”, but the person cannot read the authorized material. Return the usable-access question to the provider with the actual failed use and applicable grant.
Treating one label as one subject. A report counts “completed trips” without distinguishing journeys, business results and administrative cases. State which result is counted and retain any correspondence needed for the decision.
Expanding every request into service redesign. A handler sends an eligible ordinary request into a discovery workshop. Use the adequate existing instruction; reserve redesign for a repeated or unresolved arrangement problem.
ADM.1:9 - Consequences
The handler gains a clearer service boundary and a smaller next task. This can make hidden provider failures and participant burden visible. It shows which conclusion the administrative evidence supports when the business outcome is reported separately.
The result is limited by the available service conditions and context. If an organization has not assigned responsibility for the needed condition, identifying that gap is useful but does not supply the missing provider commitment.
ADM.1:10 - Architectural Rationale
The enabled work is the starting point because it explains why the administrative condition matters. The administrative result remains separate because it has its own applicability, provider and completion evidence. This separation supports both a simple direct request and a service spanning several providers.
A department-first boundary can be adequate when one provider already supplies the entire needed condition. It becomes inadequate when a local completion leaves the participant unable to work. A whole-business boundary has the opposite cost: it can make administration responsible for results it neither decides nor supplies.
ADM.1:11 - SoTA-Echoing
The practice question is how to define an administrative result at enough scope to help the participant without absorbing the whole business task. Keep the enabling administrative service distinct from the participant’s business work, and use OPS.3 to distinguish cases, work and descriptions. Use C.32.MWA when the answer depends on the relations among several structures.
An alternative is to define success by completion of a department’s task or delivery of a catalogue item. GOV.UK’s whole-problem service guidance is a useful comparator because it expands attention to the user’s needed outcome while cautioning against an oversized service. In §§4.1–4.3, use that contribution to start from the needed condition, follow the relevant provider joins, and keep the business outcome separate. At the same first-pass effort, one condition sentence can expose a missing result that a ticket label conceals; investigate the wider service when resolving the remaining issue could justify the extra work.
The July laboratory, especially 11:56–14:59 and 20:37–30:49, supplies reported situations and conceptual distinctions used in this synthesis. The GOV.UK guidance supplies a service-design comparison. The organization’s rules determine local administrative authority; observations of the service are needed to judge an improvement claim.
Reconsider this selection if actual cases show that the stated condition fails to distinguish administrative completion from the enabled result, or if a smaller existing service instruction gives the same needed boundary more reliably.
ADM.1:12 - Relations
ADM.2 supplies participants and organizational relations when those facts determine the request. ADM.3 resolves effectivity or change; ADM.4 compares accounts after their subjects are identified.
OPS.3 supplies the general case/work/description distinction. C.32.MWA supplies a comparison of several structures when their non-matching boundaries affect the decision. The administrative handler uses the applicable service instruction for the next administrative action on the bounded question. Return a business question to whoever is responsible for that work.
ADM.1:End
ADM.2 - Establish the Relevant Participants and Relations for an Administrative Action
Type: Architectural
Status: Stable
ADM.2:0 - Use this when
Use this pattern when an administrative action depends on the relations among the participants: who may receive a service, who is responsible for it, who may decide, or who may perform the resulting action. Typical signals are “the employee is in the directory”, “management approved”, or “the administrator can do it” without the relation needed for this request.
The subject is the organizational relation on which the administrative action depends. The first result names its participants, applicable conditions and grounds, or identifies the missing relation and the source or authority needed to establish it.
Reuse an adequate supplied assignment, entitlement or grant. If the only problem is a failed technical action under already established conditions, pass that problem to the provider using the existing instruction.
ADM.2:1 - Problem frame
A requester can act for a beneficiary. The policy owner can define the terms of service while a different holder decides an individual request and an authorized operator or service implements the decision. Identify the relations among the participants, resources and actions that the rule requires.
A role title is a useful clue to the source of those relations. It is insufficient when the intended action depends on a particular appointment, delegation, permission or obligation. A participant can fill several functions, each under its own conditions. The inquiry concerns the relation required for the action, rather than a count of departments or job titles.
ADM.2:2 - Problem
How can a handler identify the participants and organizational standing that actually determine an administrative action?
If the handler substitutes an authenticated identity or a familiar role label for the relevant relation, the service may be provided to an ineligible recipient or refused to someone whose valid relation is missing from the convenient record. If decision authority and technical capability are conflated, an implementation action can silently replace a required decision.
ADM.2:3 - Forces
Ordinary handling should reuse reliable facts and familiar responsibilities. A consequential action may nevertheless depend on a narrower grant or a different effective interval. An organizational chart makes people findable, but it may not show the counterparty, covered action or authority that this case needs.
The handler also needs a usable return when a relation cannot be established. Seek the delegation or eligibility fact that the rule requires when identity is already established.
ADM.2:4 - Solution
ADM.2:4.1 - Name the action and the participants it requires
Start with the proposed administrative action or needed condition. Identify the participant who would receive it and the provider expected to supply it. Distinguish the requester from the beneficiary when that difference affects the rule.
Then identify who may decide the unresolved question and who may perform the decided action. Include the parties whose standing or contribution determines whether the action can proceed. A direct request with one authorized provider may require only a short sentence; a delegated payment may require the principal, delegate, payee and responsible treasury performer.
If a name, identifier or account may identify a different participant, resolve that identity question before attaching organizational standing to it. SIE.5 supplies cross-source identity work when ordinary supplied evidence is inadequate.
ADM.2:4.2 - Recover the relation needed for this use
State the relation in ordinary language with its participants: “Mara holds the appointment covered by the archive eligibility rule”, “the archive custodian may grant read access to collection R”, or “Lee may configure the access that the custodian has granted”.
Recover the applicable source and conditions. Ask what establishes the relation, what action or resource it covers, when it applies, and which restrictions or ending conditions govern this use. A supplied current assignment can answer this inquiry directly. OCE.6 provides assignment results for an organizational-change question; reuse one only for the participants and responsibilities it actually establishes.
A.6.REL governs the underlying distinction between a relation obtaining and someone asserting or recording that it obtains. Its ordinary branch permits a readable relation statement. Add an occurrence identifier or a full relation model only when later work needs to distinguish another occurrence of that relation, including a later episode with the same participants.
ADM.2:4.3 - Keep eligibility, decision authority and performance distinct
For the intended action, ask which relation supplies each necessary condition. An effective appointment can make a person eligible to request access. A valid grant can permit a particular read action. A separate assignment and permission can allow a technical operator to configure the resource.
These facts can be supplied together in a well-designed service instruction. Keep them separately recoverable when a failure, restriction or later use depends on the difference. A.2.8.PER supplies the distinctions between granted permission, actual exercise and a finding of non-prohibition. A finding that no prohibition was located cannot fill a missing grant where the applicable rule requires one.
When a grant and another governing requirement imply incompatible conclusions for the same participant’s action, identify the conflicting claims and their overlapping scope and time. First apply an existing precedence rule when its stated conditions select which claim governs that use. If the rule does not settle the conflict, reuse an adequate existing authorized decision or ask the holder of authority over this conflict to decide which claim governs the specified action, scope and interval. Until a rule or such a decision settles it, return that question as unresolved. Do not infer precedence from record recency, seniority or technical capability alone.
ADM.2:4.4 - Return the usable participant account or the specific gap
The first result can be a short statement attached to the request. Name the relevant participants, the relation needed for each action, its effective conditions and the grounds that the receiving decision needs. Keep an unsupported relation claim explicit as a claim requiring resolution.
For example, “the supplied appointment establishes eligibility from 1 October; a read grant is still needed from the archive custodian” is actionable. “More approvals required” conceals the missing result and its authorized source.
Use available evidence to establish a missing fact, obtaining it from a competent source if necessary. Apply the governing rule to a disputed case when the rule settles it. A missing grant or decision that the rule leaves open goes to its competent holder. If a valid condition is already met and provision failed, send the provider the authorized action and actual failure.
ADM.2:4.5 - What changes in practice
The handler uses established relations and resolves questions from the available evidence and rules. Where a missing contribution requires another source or authority, identify the question for that holder. Identity, eligibility, decision authority and technical performance support different parts of the request. The authorized action can proceed when its conditions are met.
ADM.2:5 - Archetypal Grounding
ADM.2:5.1 - One access request, three different grounds
This constructed case concerns Mara reading collection R on 2 October for experiment E. The supplied archive rule makes an effective research appointment an eligibility condition. It authorizes the archive custodian to grant access and assigns technical configuration of an approved grant to Lee. The following case facts are supplied:
| Relevant relation | Supplied fact | Administrative consequence |
|---|---|---|
| Research appointment | Mara’s appointment is effective from 1 October and covers experiment E. | The appointment satisfies this case’s stated appointment condition on 2 October. |
| Read grant | The custodian’s valid grant permits Mara to read collection R during October. It excludes downloading. | The permitted action is reading within that scope and interval. |
| Configuration responsibility and permission | Lee is assigned and permitted to configure the granted access. | Lee can perform that configuration; a different access decision remains with the custodian. |
The handler can now ask Lee to repair Mara’s failed login under the read grant. The result of this pattern is the participant and relation account that makes that request legitimate and precise. Whether Mara can actually read the collection still depends on successful provision.
A download request is a different action. The handler can state that it falls outside the supplied grant and return it through the archive’s applicable decision route. The read grant is not widened by the technical availability of a download button.
ADM.2:5.2 - A familiar name identifies the wrong person
A directory contains two people named Mara. The appointment refers to one and the account request to the other. The handler first establishes the participant identity using the relevant sources. The appointment cannot be applied to the second person merely because the name matches.
If the identity and appointment were already unambiguous in an adequate request, the handler would reuse them.
ADM.2:5.3 - An applicable rule and an unresolved conflict
In both branches of this constructed case, Mara has the valid October read grant for collection R. A current security restriction prohibits reading that collection from 09:00 to 11:00 local time on 2 October. Her intended read is at 09:30. The grant and restriction therefore give incompatible conclusions about the same participant, action, collection and interval. The supplied authority account names the archive policy owner as the person authorized to resolve this kind of conflict.
In the first branch, an applicable policy explicitly gives that temporary security restriction precedence over read grants during the stated interval. The handler applies the rule and returns its result: the restriction governs Mara’s 09:30 read, so that action cannot proceed under the grant. No further discretionary decision is needed to settle this inquiry. The result concerns the stated overlap; it does not rewrite the October grant.
In the second branch, the same grant, restriction, intended action and decision authority are supplied, but no applicable precedence rule or existing resolving decision is available. The handler returns the particular unresolved question to the archive policy owner: which claim governs Mara’s read of R at 09:30 within the 09:00–11:00 restriction? Naming that person does not supply the answer. The handler does not authorize the disputed read from these inputs.
ADM.2:6 - Bias-Annotation
Organizational charts and provider tools tend to foreground staff and ignore claimants, contractors, external counterparties or people represented by someone else. Include a participant when the requested action depends on their relation, even if the convenient tool has no field for it.
Visible seniority can also bias a handler toward assuming authority. Recover the action-specific basis when it matters; expertise, employment, ownership and permission can have different implications under the supplied rule.
ADM.2:7 - Conformance Checklist
For the named action, examine whether:
- The requester, beneficiary, provider and decision maker are distinguished where their difference matters.
- The needed relation is stated with its participants and applicable rule or adequate supplied result.
- Its action, resource, interval and relevant restriction fit this use.
- A role title, authenticated identity or technical capability has not replaced a missing institutional condition.
- The result distinguishes an established relation, an unresolved claim and a missing decision.
- If a contribution is missing, the request names what is needed and its competent source, or identifies the unresolved responsibility.
The participant account supports the receiving action only within those conditions. It does not establish that the action was performed.
ADM.2:8 - Common Anti-Patterns and How to Avoid Them
Using the organizational chart as a universal permission table. A person’s department is known, but the requested expenditure exceeds the supplied delegation. Recover the delegation for that action and return the uncovered decision to its competent holder.
Asking the technical operator to decide entitlement. A provisioning team receives “please make it work” although eligibility is unresolved. Obtain that decision first, then give the operator the resulting action and scope.
Repeating the wrong check. Another identity check is requested when the actual missing fact is whether an appointment is effective. Reuse adequate identity evidence and resolve the relation or time question.
ADM.2:9 - Consequences
A precise participant account can reduce misdirected questions and make delegated actions intelligible. It also exposes places where an organization has no clear deciding or provision responsibility.
The account may require qualified interpretation of a policy or relation. That can limit the dependent action. A supported eligibility result can remain useful while a distinct permission question is unresolved.
ADM.2:10 - Architectural Rationale
The pattern begins with the action because that determines which relations matter. Starting from every relation a participant has would make an ordinary service request unnecessarily large. Starting from a job title alone would lose the conditions that justify the action.
General relation and permission instructions remain with their FPF suppliers. For the administrative action, establish whose institutional standing supplies the requested condition, whose decision is needed, and which provider can act on it. A short statement may suffice when the relations and their grounds are clear.
ADM.2:11 - SoTA-Echoing
The practice question is how to use organizational standing without confusing identity, eligibility, decision authority and provision. A.6.REL explains how to establish whether a reported relation holds. For a permission question, A.2.8.PER distinguishes a valid grant, its exercise and a finding that the action is not prohibited. The laboratory cases illustrate how to distinguish the rule owner, handler and provider in a request.
One alternative is to infer entitlement from a directory identity, organizational title or technical account. NIST SP 800-63-4 is a bounded comparator: its identity-proofing, authentication and federation model helps identify what a digital-identity result actually establishes. It does not decide this archive’s eligibility or read grant. That comparison changes §§4.1–4.3 and the access case: retain the supplied identity result and obtain only the different relation that remains missing. The extra explicitness is justified when that difference changes the action; adequate combined inputs can still be reused directly.
The May and June laboratory discussions provide failure examples and the specialist/handler distinction. OCE.6 explains how to establish assignments for organizational change; reuse an applicable assignment under its terms. Neither a reported incident nor an identity standard proves that a local authority relation obtains; the supplied rule and case facts do that work.
Reconsider how the handler establishes participant standing and authority for the intended action if a different institutional regime changes who can decide, if a grant’s beneficiary or scope cannot be resolved by these instructions, or if a simpler available method preserves the same action-changing relations more reliably.
ADM.2:12 - Relations
ADM.1 supplies the needed administrative condition when the action is unclear. ADM.3 determines the relevant effective time or relation change. ADM.4 handles incompatible or differently organized accounts of the participant or relation.
A.6.REL supplies relation obtaining and conditional occurrence identity. A.2.8.PER supplies the permission distinctions. OCE.6 can supply an adequate effective assignment; SIE.5 supplies identity resolution when sources do not select the participant reliably. Return the established facts to their recipient. If a service decision or provision follows, apply its existing instruction within the conditions those facts support.
ADM.2:End
ADM.3 - Determine What Changed in Administrative Relations and When It Takes Effect
Type: Architectural
Status: Stable
ADM.3:0 - Use this when
Use this pattern when an administrative question depends on whether an appointment, grant, obligation or other organizational condition has begun, continues, is suspended or has ended. It also applies when a changed record is being treated as a changed relation.
Identify the organizational relation and the time at issue. Report whether the condition held then and what, if anything, changed. If the governing rule or a fact remains unknown, identify the missing result and the source or authority that can establish it.
If an adequate supplied result already establishes the condition for the intended time, use it. Reconstruct a history when the answer depends on another date, episode or disputed change.
ADM.3:1 - Problem frame
An organization can approve an appointment before it takes effect. A directory can be updated before or after that date. A handler can learn about the appointment later still. These moments matter to different claims.
The same issue occurs with payment, delegation, cancellation and suspension. A payment instruction can exist before its effect is known. A corrected amount in a report can change what the organization claims without changing the earlier transfer. Some governing rules, however, make a particular registration or notice part of the act that changes the relation. The handler must recover that rule rather than assume that records are always constitutive or always merely descriptive.
ADM.3:2 - Problem
How can a handler determine the organizational condition applicable to one action without turning a record date, a later discovery or an intended future change into a present fact?
The wrong time can cause premature access, an incorrect refusal or a claim that a later correction retrospectively supplied missing authority. A useful answer identifies the relevant state and, when needed, the next action warranted by the available evidence.
ADM.3:3 - Forces
Current handling needs a quick usable answer. Historical disputes may require a more precise account of what was effective and what participants could then know. A convenient latest record reduces search but can conceal future applicability or a gap between two episodes.
Time detail also has a cost. Dates, time zones and interval boundaries matter only as finely as the receiving question requires. The governing rule determines the relevant precision; adding timestamps without identifying the changed relation creates false exactness.
ADM.3:4 - Solution
ADM.3:4.1 - Fix the relation and the time of the intended use
State the condition the administrative action depends on. If the relation or participants are unclear, use ADM.2. Name the time being asked about: eligibility for a request on 25 September, a grant during a session, or an outstanding obligation after a particular payment.
Keep the time of the intended action separate from the time at which the case is examined. Later evidence may improve a historical account. It does not by itself change which rule or relation applied at the earlier moment.
ADM.3:4.2 - Recover what can make the condition change
Use the applicable rule to identify the relevant act or event and its conditions. The rule may make an authorized decision effective on a stated date, require another participant’s acceptance, require a registration, or give a cancellation effect only after notice. Obtain the qualified interpretation when that requirement is unresolved.
Recover the actual case facts needed by that rule. An appointment document may be adequate evidence of its stated decision and effective date. A future plan supplies an intended change, not a completed change. An unconfirmed event remains unresolved for any conclusion that depends on it.
A.6.REL supplies the distinction between relation change and assertion or description change. Apply the direct relation’s obtaining and continuity conditions; the record’s location or revision date does not replace them.
ADM.3:4.3 - Separate the relevant times
Distinguish these times when their difference matters to the conclusion or the next action:
| Time question | What it identifies |
|---|---|
| When did the relevant act or event happen? | The decision, notice, transfer or other occurrence relied on. |
| When does the relation or condition begin, change or end? | The effective boundary under the applicable rule. |
| When was the event observed or learned about? | The evidence or participant knowledge available at that moment. |
| When was the record created or corrected? | The history of the assertion or description used to represent the condition. |
Use the same fact for several questions when it answers them for the required use. Where a deadline crosses time zones or a suspension begins within a day, recover the rule’s actual time basis before judging the boundary.
ADM.3:4.4 - Determine whether the condition holds at the requested time
Apply the rule to the facts for the requested time. State whether the relevant condition holds, does not hold, or remains unresolved on the available basis. A supported negative result settles that condition for the stated participants, basis and time. When the rule excludes this basis, report that result. When the available facts do not settle it, preserve the uncertainty even if the form offers only a binary status.
For a later history that must distinguish episodes, use the direct same-versus-new-occurrence rule under A.6.REL. The same person and role can participate again after an earlier appointment ended. A new record alone does not establish another episode; a reused identifier alone does not establish continuity.
When only the description was corrected, update the account and retain the correction history needed for its use. A claimed cancellation, suspension or new grant requires the corresponding governing act and conditions.
ADM.3:4.5 - Return the effect on the actual request
Give the handler the conclusion for the relevant action and time, its decisive basis and any remaining condition. A small timeline is useful when the ordering itself explains the answer.
Return the established positive or negative result to the handler, who applies the service rule for the response or case decision it actually requires. If another basis, a disputed interpretation or an exception is a live unresolved question, name that question and the source or authority able to resolve it. The negative result alone does not create such a question. Correcting the account and deciding whether any earlier handling needs a remedy are separate tasks; the appropriate authority selects or authorizes any remedy the rule calls for. Its provision belongs to the participant assigned to carry it out.
This inquiry can finish with an established positive or negative result, or a precisely bounded unresolved claim. A later eligibility or transition decision is a distinct result when the actual service or change question requires one.
ADM.3:4.6 - What changes in practice
When a familiar operation does not give a usable temporal answer, recover how it performs the required check. FPF B.1.5.EW helps identify that connection, its conditions and a constituent operation to learn, obtain or correct. The worked case in §5.4 applies this question to choosing and comparing dates. An understood connection can be used directly.
The handler can use a future appointment for the interval it actually covers, preserve a valid relation despite delayed recording, and distinguish a corrected report from a changed institutional condition. If a question remains open, identify the missing rule, event or effective boundary.
ADM.3:5 - Archetypal Grounding
ADM.3:5.1 - An appointment recorded before it is effective
In this constructed case, the supplied appointment rule makes an authorized appointment effective on the date stated in the decision; entry in the directory reports it. The archive’s eligibility rule requires an effective appointment. The case supplies these facts:
| Local date | Fact | Consequence for the access question |
|---|---|---|
| 20 September | The competent person makes Mara’s appointment decision, stating an effective date of 1 October. | The decision exists; its stated appointment condition concerns the later interval. |
| 22 September | The directory is updated with that appointment and effective date. | The record is available; updating it has not advanced the stated effective date. |
| 25 September | Mara requests access for that day. | The supplied appointment does not satisfy the effective-appointment condition for this date. |
| 1 October | The appointment becomes effective under the supplied rule and facts. | It can supply the appointment condition for a later request within its scope. |
The handler returns: “This appointment begins on 1 October and does not meet the effective-appointment condition for 25 September.” With only the supplied appointment and rule, that negative result completes the temporal inquiry. The handler uses the applicable service instruction for the required response to the request. If the service rule requires a separate decision, use this established date as an input to it.
Now add a different fact: Mara claims a second appointment, said to begin on 20 September, but its issuing decision and scope are unavailable. The October appointment’s negative result remains established. The handler asks the issuing appointment office to confirm whether the separately claimed appointment covers Mara, the relevant work and 25 September.
For a request on 2 October, the appointment condition can be adequate. A separate valid read grant and actual usable access still matter to that action. If both institutional inputs are already supplied and login fails, the provider receives the technical provision problem.
ADM.3:5.2 - A late record and a constitutive registration are different cases
Suppose the same appointment rule applies, but the directory is not updated until 3 October. The authorized decision and its 1 October effective date are adequately evidenced. The handler can establish the appointment condition for 2 October and correct the directory’s account. The delay in recording does not move the appointment’s effective date under this rule.
Now consider a different, explicitly supplied rule for a resource reservation: the reservation becomes effective only when the authorized allocation is entered into the designated registry. The case supplies an approved allocation at 12:00 and the required registration at 13:00, with all other conditions met. Before 13:00 the rule’s constitutive condition is incomplete; afterward it is complete. Here registration matters because the rule assigns it that role.
The handler therefore asks what the actual rule makes effective. “The record is missing” alone cannot distinguish absent evidence, incomplete constitution and a reporting defect.
ADM.3:5.3 - The same participants after a gap
A history query asks whether Mara was appointed continuously through November. The supplied rule and records establish an appointment ending on 31 October and a later appointment beginning on 1 December. The same person, organization and role do not fill the November gap. The handler retains the separate intervals needed for the historical account. If a different basis is claimed for November, establish whether it covers the gap.
ADM.3:5.4 - The date comparison within request examination
While examining Mara’s 25 September request, the handler compares that date with the appointment’s 1 October effective date. This comparison performs the temporal part of checking the required appointment condition. Through that check, the handler performs part of examining the access request. The supplied rule, Mara’s appointment and the time of intended use connect those operations.
A handler might instead compare 25 September with the directory’s 22 September entry. The calendar comparison can be correct while failing to answer whether the appointment condition holds. The repair is to recover which event and date the applicable rule makes decisive, then repeat the temporal check using that basis. Reuse the already adequate appointment decision. Someone who cannot make this rule-to-fact connection needs to learn that operation or obtain a qualified interpretation they can use in the check.
The reservation case in §5.2 changes the connection: its supplied rule makes registration at 13:00 decisive. Copying the appointment case’s treatment of registration would now produce the wrong condition. Being able to compare times does not supply the ability to identify their institutional meaning.
The date comparison is part of the same handler’s examination of the request. Count that work once. A permission decision may use its temporal conclusion. If access is granted on an applicable basis, the provider can configure it. Evidence of the researcher’s subsequent use would establish whether they read the document.
ADM.3:6 - Bias-Annotation
The latest convenient record can dominate the account even when it describes a future state or was corrected late. Conversely, a participant’s recollection can be treated as decisive without the applicable rule. Keep both the facts needed to determine the relation and the evidence limits needed to rely on the account.
A retrospective reader has knowledge that the original handler may not have had. Distinguish the relation that applied then from the information available then when judging the earlier action.
ADM.3:7 - Conformance Checklist
For the requested time, examine whether:
- The relation or condition and its participants are clear.
- The applicable rule identifies what makes it begin, change, continue or end.
- The relevant act or event and its effective boundary are supported or explicitly unresolved.
- Observation and record times remain separate where they change interpretation.
- A later correction, repeated name or reused identifier has not supplied an unsupported continuity or historical-authority claim.
- The return states what the finding establishes for the request and, if a contribution is missing, who can supply it or which responsibility remains unknown.
The same result can be reused while the relation, time, governing conditions and relied-on facts remain adequate.
ADM.3:8 - Common Anti-Patterns and How to Avoid Them
Treating future registration as present eligibility. A directory shows next month’s appointment. Apply the effective date to the intended action.
Assuming that every record merely reports. A reservation rule expressly requires entry in a designated registry before the reservation is effective. Inspect that constitutive condition rather than copying an appointment example’s different rule.
Repairing history by overwriting the latest row. A corrected report makes an earlier decision appear authorized without identifying any valid earlier basis. Preserve the difference between correcting the account and establishing what actually applied.
Inferring continuity from the same participants. A later appointment repeats the same person and role after a gap. Apply the relation’s episode rule for the history being asked about.
ADM.3:9 - Consequences
A time-specific answer can prevent premature action and avoid refusing a valid current relation merely because its usual record lags. It makes historical disagreement more precise: a dispute can concern the effective event, the evidence available then or a later description.
The cost is recovering the rule and enough history for the question being answered. When that basis is missing, return the precise unresolved condition. Changing the relation or validating an earlier action requires the authority and conditions specified by the governing rule.
ADM.3:10 - Architectural Rationale
The relation and requested time come first because they select which events and records matter. A full chronology would otherwise collect detail irrelevant to the question about the relation. Separate time questions become useful only when their answers differ consequentially.
Using the latest status alone is adequate when it reliably states the condition for the relevant interval and no live contrary fact remains. It is inadequate for future changes, delayed reporting or contested episodes. Use a timeline when those differences are material and the available account leaves them unclear.
ADM.3:11 - SoTA-Echoing
The practice question is how to distinguish an effective organizational change from a change in what participants know or record. Use A.6.REL to establish whether and when the relation held. The laboratory cases show why the record of that relation can have a different date.
One alternative is “use the latest row as the current state”. Its advantage is low handling effort. It fails when recording time is taken as effective time without the governing rule—for example, by treating a future appointment as already effective or delayed reporting as a delay in the relation itself. Under a different rule, registration can constitute the relation. Sections 4.2–4.4 and the paired registration cases retain the rule that determines which interpretation applies. The practitioner can still use an adequate latest account directly; add a timeline when it helps establish a consequential difference in what was effective or knowable.
The May laboratory’s relation/record discussion and the later ADM source pack’s effective-condition distinctions explain how selecting the wrong event can give an incorrect effective date. A.6.REL supplies the general method for relation change and optional occurrence identity. FPF B.1.5.EW supplies the explanation of constituent and encompassing work applied in §5.4.
Reconsider the instruction when a governing relation uses an additional constitutive condition, when repeated episodes cannot be distinguished for the required history, or when a new record arrangement changes what evidence a handler can obtain.
ADM.3:12 - Relations
ADM.2 supplies the relevant participants and relation when those are not already established. ADM.4 receives a source-account disagreement that remains after the time questions are explicit. ADM.1 supplies the intended administrative condition and deadline when they are unclear.
A.6.REL supplies the relation’s obtaining, continuity and conditional occurrence-identity discipline. The qualified policy or relation source supplies the actual constitutive and effective conditions. Return the conclusion for the requested time. If it is needed for service handling, use it under the applicable instruction. For an unresolved eligibility or remedy decision, take the relevant facts and question to its competent holder.
ADM.3:End
ADM.4 - Reconcile Participant-Relative Administrative Accounts
Type: Architectural
Status: Stable
ADM.4:0 - Use this when
Use this pattern when participants describe an administrative event or condition differently and that difference affects a required finding or administrative action. “We paid”, “we received”, “the account is active” and “the case is closed” can each be correct within one purpose while leaving another participant’s question unanswered.
The subject is the administrative event or relation being described, together with the participant accounts needed to answer the administrative question. The first result is a usable correspondence that preserves each correct meaning, or a precise unresolved claim and its next resolver.
If the records already concern an unambiguous subject and supply adequate compatible facts for the action, use them directly. Reconciling accounts does not require a common database or a redesign of every source schema.
ADM.4:1 - Problem frame
Several participants can be involved in one transfer, appointment or provision. Each keeps records for its own decisions. A payer records an outgoing payment; a recipient records an incoming receipt. An appointment owner records an effective assignment; a service provider records technical access. The first pair may describe one event differently, while the second pair may describe different related conditions.
A shared label, identifier or screen can conceal that distinction. A useful account identifies the subject, the claim made about it, the participant’s position, the relevant time and the question or action the claim must support.
ADM.4:2 - Problem
How can participants use their accounts together without erasing a correct difference or inventing agreement about an unresolved fact?
Forcing every record into one meaning can remove the creditor’s claim or the specialist’s qualification. Preserving every wording difference without examining its subject can leave an ordinary administrative action blocked. Establish the correspondence the administrative question requires.
ADM.4:3 - Forces
A common event account helps coordination and reduces contradictory copying. Local accounts retain purposes, authority and distinctions that the shared representation may omit. The practitioner needs to proceed with an adequate subset of facts while preserving uncertainty that affects the conclusion or decision.
The comparison must also separate representation from effect. To establish a transfer, grant or relation, identify the governing act and its evidence. Registration itself may be that act under the applicable rule. Conversely, different entry times need not mean that participants describe different events.
ADM.4:4 - Solution
ADM.4:4.1 - Start with the receiving question
Establish what each participant needs to know, decide or do. A payer may need to establish whether an obligation is discharged; a recipient may need to allocate a receipt to an invoice. Return the correspondence that answers the question, with its implications for any action the participant must take.
Recover each source statement in its own terms. Ask what the participant means by “paid”: an instruction was issued, a transfer settled, or a particular obligation was discharged under an applicable rule. Retain the author, source, intended use and time when those facts affect interpretation. A source’s authority matters to the claim for which it is used.
If a supplied statement is already clear and adequate, use it.
ADM.4:4.2 - Identify the subjects before comparing the claims
Determine whether the statements concern one subject, different subjects, or subjects whose identity remains unresolved. Use the information appropriate to the actual event or relation: participant identities, the relevant action, source reference and its issuer, amount and currency where applicable, effective time and supporting evidence.
A matching local identifier is evidence to interpret within its source scheme. It does not alone prove event identity. Repeated participants can also take part in another event. Use SIE.5 when the cross-source identity question cannot be resolved from adequate supplied facts; SIE.4 and SIE.6 supply the needed alignment and claim-composition methods for a substantive meaning problem.
For a relation history, use ADM.3 and the direct A.6.REL identity rule only as far as the receiving use needs. A different edition of a claim can still describe the same relation.
ADM.4:4.3 - Choose the correct comparison result
Distinguish three situations:
| Situation | Result and next move |
|---|---|
| Correct participant-relative accounts of one subject | Preserve each account’s meaning and state the correspondence needed for the participant actions. An outgoing payment and an incoming receipt can both describe the same transfer. |
| Different or related subjects | Establish how they are related, if at all, and use the appropriate facts for each question. A payment instruction, the resulting transfer and an obligation are different subjects; a label such as “payment” can refer to any of them. |
| Incompatible claims or an unresolved fact about the relevant subject | Preserve the exact claim and uncertainty. Obtain the evidence, qualified interpretation or authorized correction that can resolve it before relying on that disputed conclusion. |
These situations are distinguished by the case facts and meanings, not by a preference for agreement. Several can occur in one case: the parties can identify the same transfer and still disagree about the fee or its effect on an obligation.
ADM.4:4.4 - Retain only the correspondence needed for use
State the subject of each account and, where they concern the same subject, how each account refers to it. Keep the local purpose, participant-relative meaning, effective time and authority or evidence qualification that bears on the required conclusion or action. A short joined explanation can be enough.
For the payer/recipient case, retain that A17 calls transfer T a disbursement by P and B82 calls T a receipt by Q. The shared event description can say that 300 moved from P to Q at the evidenced time. P and Q then apply their supplied conditions to their different administrative decisions.
Correct a source record only through the source’s appropriate authority and procedure. A useful cross-source explanation does not authorize overwriting a participant’s account or silently replacing its rule.
ADM.4:4.5 - Return the remaining question and stop
If the correspondence and supplied facts answer the receiving question, return the conclusion for that use. Where action follows, use the correspondence under the applicable instruction. Keep the correspondence available for work that depends on it.
If an amount, time or effect remains unknown, state the exact missing fact and establish it from available evidence or seek it from a source or checker able to supply it. For a disputed institutional condition, apply a governing rule or existing decision that settles it. Return any remaining decision to its competent holder. A technical retry is appropriate only after the state and applicable recovery rule are adequate; a missing settlement confirmation is not a reason to issue a potentially duplicate payment.
The reconciliation can finish with a correspondence plus one bounded unresolved claim.
ADM.4:4.6 - What changes in practice
Participants can retain different correct descriptions and still coordinate. A handler can also distinguish a meaning problem from an unknown effect, a wrong identity or a rule question and request the right next result. Consistent wording becomes a means of understanding the event, rather than a substitute for establishing it.
ADM.4:5 - Archetypal Grounding
ADM.4:5.1 - One transfer, two correct administrative accounts
In this constructed case, organization P makes one authorized transfer T of 300 currency units to hotel Q for invoice I. The case supplies bank evidence that the full amount was credited to Q at 13:00 on 10 September, with no fee deducted. The supplied invoice terms make the full 300 credit to this destination discharge P’s 300 obligation. Q’s supplied allocation rule applies a matching identified receipt to I. These conditions, including the authority for the payment and record actions, are inputs to the example.
P enters record A17 at 13:05 and calls T an outgoing payment or disbursement. Q enters B82 at 15:20 and calls T an incoming payment or receipt. The local record-entry events differ. Both records describe the same settled transfer at 13:00.
The handler establishes the correspondence using the bank reference with its issuer, the payer and recipient, destination, amount, currency, effective time and settlement evidence. The result is:
| Account retained | Correspondence | Action it supports |
|---|---|---|
| P’s A17: disbursement of 300 to Q for I | A17 describes transfer T from the payer’s position. | P’s responsible handler records the outgoing payment and, under the supplied invoice conditions, records the 300 obligation as discharged. |
| Q’s B82: receipt of 300 from P for I | B82 describes T from the recipient’s position. | Q’s responsible handler allocates the receipt to I and updates the outstanding receivable under Q’s supplied conditions. |
Both descriptions survive because their different directions are correct relative to different participants. The common event description supplies neither spending authority nor the rule for discharge or allocation; those are explicit inputs in this case. The participants can use this correspondence without replacing their ledgers or local record identifiers.
ADM.4:5.2 - The amount differs
Now suppose P’s account concerns 300 and Q reports a credit of 290. The handler first asks what each amount measures. A fee, a gross-versus-net distinction, another transfer or a genuinely incorrect claim could change the answer.
If evidence establishes a 300 gross transfer and a 10 fee, those quantities can be compatible descriptions. Whether the payer’s obligation is discharged still depends on the applicable payment conditions. If the evidence is unavailable, identify the unresolved credit or fee and what source result would settle it. Use that result when it becomes available. Neither a shared reference nor a familiar payment status settles it.
ADM.4:5.3 - The same label names different subjects
A traveller says “the trip was unsuccessful”; the travel desk says “the trip is complete”. The traveller means the negotiations produced no agreement. The desk means the travel conditions were supplied and the expense handling completed. ADM.1 separates those subjects and their connection. Treating them as two conflicting measurements of one result would send the next action to the wrong person.
In another case, two records both show “reference 17”, but the numbers belong to different issuing systems. The handler cannot combine them until identity is established. The shared numeral is insufficient correspondence.
ADM.4:6 - Bias-Annotation
A common representation often adopts the vocabulary of the party that owns the tool. That party’s purpose and authority can then appear universal. Ask whose decision each claim supports and which local qualification would be lost by the proposed common wording.
Access can also be asymmetric. One participant may have settlement evidence that another cannot inspect. Preserve the resulting reliance limit and request an adequate permitted source return; apparent silence or lack of access is not itself proof that the event failed.
ADM.4:7 - Conformance Checklist
For the receiving administrative use, examine whether:
- The participant actions and the subjects of the source statements are identifiable.
- A claimed common identity is supported beyond an ambiguous shared label or reference.
- The comparison distinguishes compatible participant-relative meanings, different subjects and incompatible or unresolved claims.
- Relevant quantities, times, source meanings and institutional qualifications survive the correspondence.
- Each participant can identify what the result supports and what it leaves unresolved.
- A needed correction, evidence request or qualified decision reaches the competent source or decision holder.
These questions assess the usable correspondence. A separate claim that an obligation was discharged or an action was permitted still uses its governing conditions.
ADM.4:8 - Common Anti-Patterns and How to Avoid Them
Forcing correct directions to agree. A common ledger replaces both “disbursement” and “receipt” with one participant’s term. Preserve the common transfer and each participant’s relation to it.
Making the identifier do every job. A matching reference is used as proof of identity, amount, settlement and authority. Establish the correspondence, then retain the separate facts each conclusion requires.
Resolving missing effect by copying a status. A payer’s “sent” field is copied as “received” in another account. Obtain evidence of the relevant effect and preserve uncertainty until that evidence or the applicable recovery decision is adequate.
Reconciling different subjects as contradictory views. Negotiating work and travel administration are treated as one result. Identify their subjects and use the appropriate next action for each.
ADM.4:9 - Consequences
A bounded correspondence can make participant accounts jointly usable while retaining their correct differences. It can reduce unnecessary schema redesign and identify who or what can supply the missing fact.
The result may remain partial because some meaning, evidence or institutional condition is unavailable. That limitation is useful when it isolates the exact conclusion that cannot yet be relied on. It does not require withholding every independently supported fact.
ADM.4:10 - Architectural Rationale
The receiving question identifies which correspondence the participants need, whether for a historical account or for an administrative action. Subject identity precedes comparison of participant meanings because a viewpoint label cannot establish that two statements concern the same thing. Institutional consequence follows separately because a common event description cannot determine a rule it does not contain.
Alternatives include full normalization into one account and leaving every source separate. Normalization can be economical when meanings and authority already match. It loses useful content when participant-relative meanings or decision conditions differ. Separate sources can remain adequate when one action needs only one account; a bounded correspondence is worthwhile when a finding or action depends on facts from more than one account.
ADM.4:11 - SoTA-Echoing
The practice question is how to preserve correct participant-relative accounts while producing an administrative result the parties can use. Use SIE.4–SIE.6 for unresolved alignment, identity or claim composition. Once the administrative subject has been established, the Partridge comparison helps retain its meaning for each participant.
One alternative is a single normalized representation whose terminology replaces all local accounts. The Partridge papers distinguish organizing an account around a participant from describing the common represented event, and separately examine how direction is represented. Use the distinction in §§4.2–4.4 and in the payer/recipient case to establish the common event, retain how each participant describes it, and keep the next institutional action under its supplied rule. The full BORO ontology and one-database infrastructure are not selected for this bounded result.
Thoroughly Modern Accounting, especially PDF pp. 9–10 and 13–14, and Ontology then Agentology, PDF pp. 5–8, supply conceptual arguments and worked representations. They do not establish the facts of a particular transfer or empirical superiority in every administrative setting. The July laboratory and later source pack supply the distinction between different subjects and different accounts of one subject. Both contributions are needed to avoid treating every disagreement as a viewpoint difference.
At comparable handling effort, a small explicit correspondence preserves the participant meanings that matter to the question without a full schema merger. Maintaining it has a cost when source meanings change. Reconsider the selected correspondence when a new participant, source scheme, quantity, effective-time rule or institutional decision makes the retained distinctions insufficient, or when an existing integrated account already supplies them adequately.
ADM.4:12 - Relations
ADM.1 separates the enabled work and administrative result when a broad label hides different subjects. ADM.2 supplies participant standing and authority; ADM.3 supplies effective conditions and relation history. Use their results only when the receiving comparison needs them.
SIE.4–SIE.6 supply alignment, identity and claim composition for unresolved semantic integration. OPS.4 supplies usable current claims for ongoing handling. A.6.REL governs a relation occurrence and its distinction from revised descriptions when that history matters.
The responsible handler uses the correspondence with the applicable service or specialist instruction. In the transfer case, P’s handler applies the supplied obligation-discharge condition and Q’s handler applies the receipt-allocation rule. If a payment or other provision is still needed, the assigned and authorized provider follows the applicable instruction for that action. Establish the prerequisites for provision before the provider acts. The handler sends an unresolved substantive question to the specialist or decision maker competent to answer it.