ADM.Preface:3 - Different things, different accounts and different structures

First establish what each statement concerns. “The trip” may mean a journey, negotiating work or the administrative handling that enabled both. Those are related subjects with different completion conditions. By contrast, the payer’s disbursement and the recipient’s receipt can be correct accounts of one transfer. A useful common account preserves the correspondence between them.

An organizational relation also differs from a claim about it. An appointment can already be effective although a directory has not been updated. A future appointment can already be recorded although it is not effective today. Some rules make registration part of constitution; in those cases the record-related act matters because the rule makes it matter. The practitioner determines which situation applies from the supplied rule and facts.

Several arrangements can concern the same people without becoming one hierarchy. One service may support several projects; one administrative case may require several specialist decisions and providers. A shared record can help the participants coordinate while their responsibilities remain distinct. Use the actual enabling, provision, assignment and evidence relations. When a decision depends on comparing several structures, C.32.MWA supplies that comparison; the common label or shared people do not establish parthood.

Consider two projects whose researchers need archive access during the same morning. In this constructed case, each request has an adequate appointment, identity result and valid grant, but each still needs an account mapping before the archive provider can configure usable access. That mapping is a prerequisite of configuration; it is not a prerequisite of the identity check that has already supplied its result.

Both requests are ready for mapping. The same qualified specialist has one two-hour window, and each mapping requires two hours of that specialist’s work under the supplied method. Each request fits alone; together they require four hours. The responsible service parties must resolve priorities, timing or qualified additional provision under their actual commitments before promising both in that window. ADM.11 identifies the shared contribution and its receiving inputs. ADM.9 establishes the usable access after provision, and ADM.15 accounts for the recipients’ waiting and any displaced work.

The projects, requests, providers and grants therefore have different boundaries. The appointment and grant results can remain adequate while the combined provider promise is unsupported. A larger window or qualified additional capacity changes that promise question; reuse earlier results only within their scope and effective time. If the revised use exceeds those conditions, return to ADM.3 or ADM.8 for the relevant time or permission question. Use C.32.MWA when the decision needs a fuller comparison of such structures.

There is also the question of what a handler is doing through an operation. Comparing the relevant dates can perform the temporal part of checking an appointment condition, which performs part of examining an access request. The applicable rule and the facts selected for it connect these descriptions of the work. ADM.3’s worked case shows how this connection can fail despite correct date comparison. Use B.1.5.EW when you need to recover that connection or identify an operation to learn, obtain or correct; use an already understood connection directly.