Sources and direct returns
First edition
This is the first edition of the Organization Administration Principles Framework, with reference code ADM and fifteen patterns: ADM.1–11 and ADM.13–16. It offers prospective practitioner guidance for administrative conditions, cases and arrangements under the actual rules of the organization. Its constructed cases explain the instructions; claims about a particular service’s effectiveness require that service’s evidence.
Cite the framework name, release date and PatternID when the wording or source basis matters. A pattern address continues across editions only while its practical answer continues. The ToC’s Part and position locate the current presentation.
Copyright © Anatoly Levenchuk. The original framework text and worked examples are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). The licensing notice states the scope and attribution terms. Referenced third-party works retain their own terms.
External source states and refresh
Use the following source states when checking a source change or reconstructing this edition’s basis. The applied-instruction table and source arguments below name the exact sections, contributions and limits used. The hashes identify the source texts used.
ADM relies on the cited FPF relation, permission, evidence and structure distinctions and on the named OPS, OCE, SIE, SYSE and ME instructions for their stated receiving uses. Those texts remain external to ADM. Removing a needed contribution or changing its meaning can invalidate the corresponding ADM instruction or return; it reopens that use.
| External source text | SHA-256 of the relied-on source state |
|---|---|
| FPF A.6.REL | 7cc6e809db555cfda2f2d9373614810fff7f4cd411218f94b5a1e3a1315bf89f |
| FPF A.2.8.PER | c940642c546f44de1e4ec1a139a78fe6757f377ba2a7762d688074f2deaf6bc7 |
| FPF C.32.MWA | 4cc2acb560b37dff68a9f6607b1957d373f4ee3968940d77309d59c032aab4be |
| FPF A.10 | 376994b9f2837d55724e83cc9c1b6d798c6f139abbd6adbe01a614c1f3bcfea4 |
| FPF B.3 | d9b76ef38ce2f46339fe7bd10bf88a3d77ba499a1497f54ea19009496786748b |
| Operations Management | 3db33a91206c05eb21b83b51a613e1cbfb73a5925338b95fd968a4e64d548bbe |
| Organization Change Engineering | 768881ebd8655e9736f49c5d01c53816d22cfb897b8f728c2a6928203b8c9bf4 |
| Semantic Integration Engineering | 24caed612eaec96e21b59062bf6c8e6df081b75485b4a3eea00c8756c4845a31 |
| Systems Engineering | d82c411414e50a001fa9f018b1b8c1039e701435e8cf1b6d8242b229ffed7b87 |
| Method Engineering | c7f791f9f6f7ef9899f287335204a2727e35a4bf4a54b611e174c9f79dd5076c |
A changed source file calls for comparison of the relied-on sections. Unchanged contributions remain usable within their conditions. If a needed external instruction or its source cannot be recovered, retain the exact missing contribution and continue only the questions that do not depend on it. A citation supplies neither the organization’s rule nor permission to act.
Revisit an affected pattern when a real use exposes an unclear action, a missed case, unsupported evidence or an excessive burden. Revisit the connected explanation when an individual result no longer supports the next question it promises to answer. A changed source meaning, organizational rule, population or operating condition reopens only the claims that depend on it. The relevant pattern’s source return and stopping conditions identify the first place to work.
Applied framework instructions
The cited methods retain their own scope. Use the named contribution when it answers a live question; the citation is not a requirement to read every framework before handling a request.
| Source | Contribution used here |
|---|---|
| FPF A.6.REL — Relation Obtaining and Individuation: Distinguish Occurrences When Needed, §§4.2–4.7 | Readable relation use; obtaining versus assertion; occurrence identity only for a receiving use that needs to distinguish episodes; relation change versus description change. ADM.2–4 apply these distinctions to the actual administrative rule and facts. |
| FPF A.2.8.PER — Granted Permission, Exercise and Non-Prohibition, §§4.1 and 4.3–4.6 | Keep a grant, its exercise and a non-prohibition finding distinct; apply a matching conflict rule or adequate resolving decision before returning a genuine gap. ADM.2 and ADM.8 apply these distinctions to the named administrative action. |
| Operations Management, OPS.3–6, OPS.8 and OPS.12–15 | OPS.3–4 distinguish operating subjects and usable claims; OPS.5–6 supply admission and continuation. OPS.8 supplies receiving-action readiness and operational joins. OPS.12–15 supply burden, promises, financial comparison and observations for the actual decision. Administrative eligibility, authority and fulfillment rules remain explicit inputs. |
| FPF A.10 — Evidence Graph Referring, §§4.1–4.2 and 4.5–4.6; B.3 — Trust and Assurance Calculus, §§4.1–4.2 | A.10 recovers the exact claim, source and bounded reliance without supplying the domain result. B.3 is used only for an actual named assurance claim; consequence alone does not create one. ADM.7 retains these limits. |
| Organization Change Engineering, OCE.6 and OCE.13 | OCE.6 supplies an effective assignment for its organizational-change question. OCE.13 supplies bounded consequence comparison, population and evidence distinctions, and the limits of a descriptive or causal claim. Adequate results are reused within their actual scope. |
| Semantic Integration Engineering, SIE.4–6 | Supplies alignment, cross-source identity and claim composition when the administrative accounts cannot be combined directly. |
| FPF C.32.MWA — Practice-Architecture Synthesis from Several Structures | Compares several structures when their differing boundaries or relations change the practice decision. |
| FPF B.1.5.EW — Recover How Constituent Actions Enact Encompassing Work | Recovers how an operation performs encompassing work and which conditions connect them. ADM.3:5.4 applies it to temporal checking within request examination. |
| Systems Engineering, SYSE.24 §§4.1–4.9 | Compares complete obtaining arrangements for a project result. Adequate administrative permissions, responsibilities and provider conditions are inputs; the choice does not itself perform the later provision. |
| Systems Engineering, SYSE.26 §§4.1–4.5 and SYSE.28 §§4.1–4.5 | SYSE.26 supplies supported interaction, usable result and recovery of uncertain effects. SYSE.28 supplies check placement, condition-bound reuse and distinct outcomes. ADM.7 and ADM.9 use these results without requiring control or platform redesign for each case. |
| Systems Engineering, SYSE.8–9 and SYSE.29 | SYSE.8 develops provider arrangements with distinct contributions and undertakings; SYSE.9 uses adequate expert results or qualifies worthwhile missing contributions. SYSE.29 supplies actual-use transition, coexistence, recovery and retirement. ADM.11, ADM.14 and ADM.16 connect these results to institutional conditions. |
| Method Engineering, ME.15 and ME.17 §§0, 4.1 and 4.4 | ME.15 distinguishes actual method variants from changed descriptions, support or other governed objects. ME.17 governs Method Engineering practice. ADM.16:4.5 adapts its population, interval, independent-use, supported-continuation and selective-inquiry distinctions to administrative case handling, retaining their evidence limits. Direct ME.17 use concerns a Method Engineering culture question. |
Administrative and representation sources
The following source arguments shaped the working distinctions. The constructed cases in this publication are applications of those distinctions with supplied facts; they are not reports of observed ADM deployments.
Administration laboratories and synthesis
The dated laboratory transcripts and ADM-Lab synthesis are working source materials with no public full-text return supplied in this edition. The following accounts give their selected contributions, original locators and limits; the receiving ADM instructions are available in this publication.
- Administration laboratory, 1 July 2023. The transcript, especially 11:56–14:59 and 20:37–30:49, distinguishes the journey, work at the destination and administrative case; 30:52–42:21 develops participant and payment descriptions. ADM.1 and ADM.4 retain the subject and participant distinctions; ADM.9–10 connect them to usable provision and reconciliation. Reported situations and proposed ontologies do not establish universal administrative laws.
- Administration laboratory, 27 May 2023. The transcript, especially 14:53–19:40, 49:40–64:24 and 69:14–77:50, connects controls to their purpose, distinguishes relation state from records, and examines usable provision. ADM.2–3 retain the action-changing rule and record distinctions; ADM.6–9 apply the competent-check, permission and usable-provision questions. The T+N discussion at 69:14–77:50 supplies ADM.15’s qualified elapsed-delay question.
- Administration laboratory, 17 June 2023. The transcript, especially 44:18–56:43 and 62:15–78:22, separates developing a service from using it and connects substantive judgments, execution and exception resolution. This supports the Preface’s design/handling distinction, ADM.2’s competent return and ADM.5–6’s reusable instruction and exception resolution. ADM.11 and ADM.13–16 extend the corresponding provider, record, control and transition questions.
- ADM-Lab source pack v0.1, 15 July 2026. The synthesis, especially §§13–21 and 23–27, qualifies the earlier discussions. Section 15 supports the same-subject/participant-account comparison; §§20.1–20.2 propose the T+N delay question and qualify speed by reliability and participant burden. ADM.15 uses OPS.15:4.2–4.3 to make the selected start, usable end, source and time uncertainty recoverable. This is a dependent synthesis and authorial clarification, not independent corroboration.
Enabling provision and decision accounts
The administrative contribution is to make the organizational condition support the participant’s intended work and to examine the burden of obtaining that support. The accounting contribution is to choose an account that answers the operating decision while retaining accounts required for other purposes. ADM.1, ADM.9 and ADM.15 make the enabling result and participant burden explicit; OPS.14–15 supply the financial comparison and observation methods used here.
Accounting representations and TameFlow
- Partridge and colleagues, Thoroughly Modern Accounting: Shifting to a de re Conceptual Pattern for Debits and Credits, 2018. Published in Advances in Conceptual Modeling, ER 2018, LNCS 11158, pp. 134–148; public bibliographic record and abstract, DOI 10.1007/978-3-030-01391-2_20. The consulted preprint, PDF pp. 9–10 and 13–14, figures 7–8, supports the comparison of participant-relative and common representations and transaction direction. ADM.4 and ADM.10 adapt the representational contribution after event identity is established, while fulfillment remains governed by the actual obligation. The record identifies the work; its full-text download is restricted.
- Partridge and colleagues, Ontology then Agentology, 2018. The paper, especially PDF pp. 5–8, table 2 and figures 2–4, distinguishes the common represented subject from an actor’s position and meaning. ADM.2 and ADM.4 retain the useful correspondence. The conceptual examples do not establish empirical superiority of one database or require adopting the complete source ontology.
- Tendon and Doiron, Tame your Work Flow, 2020; Tendon, The Book of TameFlow, version 17 January 2022. The consulted 2020 book, chapters 6–8 and 21, and the consulted 2022 book, chapters 15–16 and chapter 17 pp. 267–276, supply historical operating arguments about readiness, commitment, financial contribution and recurring problems. ADM.11 and ADM.15–16 use the qualified OPS instructions rather than universal single-metric, fixed-cost or cultural-effect claims. OPS.14–15 supply the financial comparison and observation methods used here. Public returns are the publisher’s Tame your Work Flow catalogue page and The Book of TameFlow page. The first is retired from sale; the second presents the continuing edition. These pages identify the works; the chapter and page locators above refer to the consulted editions.
Using operational accounts
Use an account suited to the operating decision, relate workload and capacity to financial consequences, and refresh assumptions when the decision changes. Preserve other accounts for their respective purposes. OPS.14–15 describe the corresponding comparison and observation methods.
For ADM.15, use the relevant receipts, payments, time and participant burdens on the declared comparison basis. This qualified reuse supplies no universal monetary objective, no rule that all allocated cost is useless, and no general equivalence between ROI or ROMI and a customer-value-to-acquisition-cost ratio. A cash comparison uses its declared incremental receipts and payments; a broader investment or customer-value claim requires the applicable finance or accounting method.
Bounded current comparisons
GOV.UK’s Service Standard, point 2 supplies the whole-problem service comparison used in ADM.1 and ADM.11. Its user-problem boundary is useful here; it does not establish the authority, applicability or outcome of a local administrative service.
NIST SP 800-63-4, Digital Identity Guidelines, July 2025, particularly its digital-identity model and Redress section, distinguishes identity proofing, authentication and federation and supplies bounded issue-handling and correction guidance. ADM.2 and ADM.6–7 retain the distinction between the needed identity result and a separate eligibility or permission condition. The federal digital-identity scope does not determine local entitlement.
OMG CMMN 1.1, 2016, §§4.1–4.3, supplies the case-outcome, information and model/execution comparison used in ADM.5–6. It does not supply institutional authority or imply CMMN conformance here.
OASIS XACML 3.0, 2013, terminology and §7.2, supplies the policy-decision/enforcement comparison in ADM.8 and ADM.14. Its enforcement obligations are operations within that architecture; they are not imported as general legal duties.
ISO 15489-1:2016’s public abstract supplies the records, metadata, responsibilities, business-context and controls comparison in ADM.13. The full paid standard and its individual clauses were not inspected; the abstract supplies no local retention period or compliance conclusion.
Goth, Catala-Perez and Hedderich’s 2025 shared-service cost review is used through its author-institution abstract. Its qualified concern about weak or unclear company-wide financial baselines limits a general administrative-cost-reduction claim in ADM.15. The full article was not read; the finding does not establish that shared services never save cost.