APQC PCF vs the Organizational Platform's function/motion tree — what to borrow, what to build

The question

Verbatim from the Notion Research Backlog: "What established frameworks cover function/motion decomposition of organizations (APQC PCF, BIZBOK capability mapping, operating-model design, GTM-motion literature, industry reference models), and what should the organizational-platform's function/motion tree borrow vs build?"

Scope narrowed 2026-08-16 to APQC's Process Classification Framework only. BIZBOK/operating-model design and GTM-motion/industry-reference-models (eTOM, BIAN, SCOR) are covered by two sibling briefs filed the same night. Consumer: the Organizational Platform build, phase 3 — the 10 function pages and 36 motion pages are frontmatter-and-spine until this framework-research round lands the hand-section template.

Terminology in this brief: our levels are function and motion. PCF's own level vocabulary (Category / Process Group / Process / Activity / Task) is named as PCF's and mapped onto ours, never merged with it.

What we already know (from the vault)

• The live engagement that stresses this taxonomy is Kwik Trip — convenience store, fuel, grocery, foodservice, plus vertically-integrated manufacturing and distribution. See [[2026-08-04-kwik-trip-ai-architecture-engagement-context]]; the platform ownership map there is drawn at director level, which is the altitude our function/motion tree has to survive at.
• The registry's own statement of what the tree is for, verbatim: "Routing + defaults. Not archetypes: archetypes are flat routers; functions drill." The tree exists to route a use case to a value shape and a role-cost backbone, not to document how work gets done.
• The role catalog's asset is the title→SOC mapping, not the rates (2026-08-08 live-test lesson). Anything a borrowed framework does to the function/motion tree has to survive the 80 role pages hanging off it.
• The vault's process-worldview note [[2026-04-03-management-is-prediction-spc]] frames a business as a process with manipulable input metrics — that is precisely PCF's worldview, and precisely the axis on which PCF and our tree differ (see the structural critique below).
• Adjacent framing: [[2026-05-26-moonshots-organizational-singularity-ep258]] argues organizations should be architected around intelligence rather than hierarchy. Our tree is a hierarchy-of-work model; PCF is a hierarchy-of-process model. Neither is the intelligence-architecture model, which is worth naming as a known limit of both.

What the web says

1. What the cross-industry PCF actually is

Read directly. I downloaded and read the full APQC-authored PDF of APQC's Process Classification Framework® — Cross-Industry, Version 7.4 (footer: "Version 7.4 • August 2024"), mirrored publicly at solutions.ifrc.org (APQC catalog code K014750). Everything in this subsection is from that document's own text unless flagged otherwise.

APQC's self-description, verbatim from the overview page: "a taxonomy of cross-functional business processes intended to allow the objective comparison of organizational performance within and among organizations... developed by APQC and its member companies as an open standard to facilitate improvement through process management and benchmarking, regardless of industry, size, or location." It "organizes operating and management processes into 13 enterprise-level categories, including process groups and more than 1,000 processes and associated activities." Origin: 1992, initial design involving APQC plus 80+ organizations. It is the backbone of APQC's Open Standards Benchmarking database.

The five levels, verbatim definitions from the "PCF Levels Explained" graphic on page 3 (I read the rendered page, since the graphic does not extract as text):

Numbering scheme, verbatim: "The PCF identifies each process element using a unique 5-digit reference number following the name of the process element... This number will always refer to the conceptual definition of the process element. The actual process elements and actual definition may change, but conceptually the decomposition will remain consistent... A new 5-digit number will be assigned to a process element if its definition substantially changes." So there are two identifiers per element: a positional dotted path (11.1.3.3.1) that is unstable across versions, and a stable 5-digit concept id (18129) that is the real key. This is the single most transferable idea in PCF and we should copy it outright — see the synthesis.

The 13 categories, with the operating vs management-and-support split exactly as the PDF draws it:

Operating processes:

1. 1.0 Develop Vision and Strategy
2. 2.0 Develop and Manage Products and Services
3. 3.0 Market and Sell Products and Services
4. 4.0 Manage Supply Chain for Physical Products
5. 5.0 Deliver Services
6. 6.0 Manage Customer Service

Management and support services: 7. 7.0 Develop and Manage Human Capital 8. 8.0 Manage Information Technology (IT) 9. 9.0 Manage Financial Resources 10. 10.0 Acquire, Construct, and Manage Assets 11. 11.0 Manage Enterprise Risk, Compliance, Remediation, and Resiliency 12. 12.0 Manage External Relationships 13. 13.0 Develop and Manage Business Capabilities

The full level-2 process-group list (extracted from the same PDF; this is the layer that actually competes with our motions):

• 1.0 — 1.1 Define the business concept and long-term vision · 1.2 Develop business strategy · 1.3 Develop and measure strategic initiatives · 1.4 Develop and maintain business models
• 2.0 — 2.1 Govern and manage product/service development program · 2.2 Generate and define new product/service ideas · 2.3 Develop products and services
• 3.0 — 3.1 Understand markets, customers, and capabilities · 3.2 Develop marketing strategy · 3.3 Develop and manage marketing plans · 3.4 Develop sales strategy · 3.5 Develop and manage sales plans
• 4.0 — 4.1 Plan for and align supply chain resources · 4.2 Procure materials and services · 4.3 Produce/Assemble/Test product · 4.4 Manage logistics and warehousing
• 5.0 — 5.1 Establish service delivery governance and strategies · 5.2 Manage service delivery resources · 5.3 Deliver service to customer
• 6.0 — 6.1 Develop customer service strategy · 6.2 Plan and manage customer service contacts · 6.3 Service products after sales · 6.4 Manage product recalls and regulatory audits · 6.5 Evaluate customer service operations and customer satisfacion [sic, APQC's typo]
• 7.0 — 7.1 Develop and manage human resources planning, policies, and strategies · 7.2 Recruit, source, and select employees · 7.3 Manage employee onboarding, training, and development · 7.4 Manage employee relations · 7.5 Reward and retain employees · 7.6 Redeploy and retire employees · 7.7 Manage employee information and analytics · 7.8 Manage employee communication
• 8.0 — 8.1 Develop and manage IT customer relationships · 8.2 Develop and manage IT business strategy · 8.3 Develop and manage IT resilience and risk · 8.4 Manage information · 8.5 Develop and manage services/solutions · 8.6 Deploy services/solutions · 8.7 Create and manage support services/solutions
• 9.0 — 9.1 Perform planning and management accounting · 9.2 Perform revenue accounting · 9.3 Perform general accounting and reporting · 9.4 Manage fixed-asset project accounting · 9.5 Process payroll · 9.6 Process accounts payable and expense reimbursements · 9.7 Manage treasury operations · 9.8 Manage internal controls · 9.9 Manage taxes · 9.10 Manage international funds/consolidation · 9.11 Perform global trade services
• 10.0 — 10.1 Plan and acquire assets · 10.2 Design and construct assets · 10.3 Maintain assets · 10.4 Manage asset end-of-life
• 11.0 — 11.1 Manage enterprise risk · 11.2 Manage compliance · 11.3 Manage remediation efforts · 11.4 Manage business resiliency
• 12.0 — 12.1 Build investor relationships · 12.2 Manage government and industry relationships · 12.3 Manage relations with board of directors · 12.4 Manage legal and ethical issues · 12.5 Manage public relations program
• 13.0 — 13.1 Manage business processes · 13.2 Manage portfolio, program, and project · 13.3 Manage enterprise quality · 13.4 Manage change · 13.5 Develop and manage enterprise-wide knowledge management (KM) capability · 13.6 Measure and benchmark · 13.7 Develop, manage, and deliver analytics · 13.8 Manage environmental health and safety (EHS) · 13.9 Manage sustainability

Current version. Version 7.4 is dated August 2024. APQC's resource library also lists a Cross-Industry PCF Version 8.0 in PDF and Excel, and APQC's own resource-collection page states v8.0 is the latest, released 2025-05-30 (secondary: search-surfaced APQC page text at apqc.org resource listing; APQC's HTML pages return HTTP 403 to automated fetch, so I could not read the page myself). Descriptions of 8.0 still say "13 enterprise-level categories" and "over 1,000 processes." I could not obtain the v8.0 full text — no public mirror found, and the apqc.org static-asset path requires the exact filename. Treat every level-2 name above as verified-for-7.4 and presumed-stable-in-8.0, not verified for 8.0.

Addendum (added at close-out, 2026-08-17): partial v8.0 text obtained — one correction, two upgrades. A background sub-agent reached the first 5 of 38 pages of the v8.0 cross-industry document (APQC item K016809). Sourcing chain, stated plainly because it is not a clean primary read: the document's listing on Scribd embeds OCR'd text of its first ~5 pages as a free SEO preview, reachable through a readability proxy; pages 6–38 remain paywalled. This is APQC's own document text at one remove, with OCR risk, and it is better evidence than the search-snippet secondary above but weaker than the direct 7.4 PDF read.

• Correction — the release date above is wrong. The v8.0 cover and running footer read "Version 8.0 • February 2026." The 2025-05-30 date in the paragraph above came from search-surfaced APQC page text and should be treated as superseded. The framework is roughly six months old, not fifteen.
• Upgrade — the 13 top categories are verified stable in 8.0, with one name change. The v8.0 table of contents matches the 7.4 list above in count, order, and numbering (1.0 Develop Vision and Strategy through 13.0 Develop and Manage Business Capabilities; 8.0 IT, 9.0 Financial Resources). The one difference: v8.0 category 7.0 reads "Develop and Manage Human Resources," where 7.4 reads "Human Capital." Taken from the v8.0 TOC as read; worth a second look before it is quoted to a client, because the label drifted back to the older wording rather than forward. The sub-agent also flagged a historical numbering shift for Financial Resources — that shift predates 7.4 and is not a 7.4→8.0 change. So "presumed-stable-in-8.0" is now verified-stable at the category level; level-2 names remain presumed only.
• Upgrade — the dual-identifier scheme survives into 8.0. This matters because section 3 below names it the highest-value thing to steal. Verbatim from the v8.0 text: "The PCF identifies each process element using a unique 5-digit reference number following the name of the process element... A new 5-digit number will be assigned to a process element if its definition substantially changes." Confirmed id: 1.0 Develop Vision and Strategy = 10002. The recommendation to decouple a stable concept id from the positional path is therefore built on a convention APQC is still maintaining, not a legacy artifact.
• Not confirmed in 8.0: the operating vs management-and-support split (it renders as a graphic, not OCR-able text), and the Category/Process Group/Process/Activity/Task level labels — the visible 1.0 → 1.1 → 1.1.1 → 1.1.1.1 numbering is consistent with the historical 5-level structure, but the label set itself was not readable.
• Upgrade — the license grant is verified current. The ©2026 v8.0 copyright page carries the same grant, verbatim: a "perpetual, worldwide, royalty-free license to use, copy, publish, modify, and create derivative works of the PCF," conditioned on the attribution paragraph. The licensing verdict in section 3 therefore holds for the current version, not just for 7.4.
• Partially closes honest gap (b) below. The v8.0 PDF listing is lead-gated — a name/email/organization form at apqc.org/resource-library/free-content/nojs?nid=604812 — and apqc.org/system/files returns 404 for v8.0 filename guesses, unlike the older Retail file which is a direct static asset. So the newest framework does require registration to download, even though it remains free of charge.
• Does not close follow-up #1. Whether CI 3.5.6/3.5.7/3.5.8 gained children in 8.0 is still unverified — those leaves sit in category 3, inside the paywalled page range. The brief's core "orthogonal axes" finding rests on 7.4 and remains open to reversal by 8.0.

2. The retail PCF — and why it under-serves a convenience/fuel operator

Read directly. APQC's static-asset path is not behind the 403 that blocks its HTML pages, so the retail PDF is fetchable: K09368_Retail Process_v721_011519.pdf. Title: "RETAIL PROCESS CLASSIFICATION FRAMEWORK® — Version 7.2.1", January 2019, 30 pages, developed by APQC in conjunction with Microsoft and stated as compliant with Cross-Industry PCF v7.2.1. Originally announced November 2012 (APQC press release).

It keeps 13 categories and the same management-and-support block (7.0–13.0 identical to cross-industry), but rebuilds the operating half:

Retail operating process groups: 2.1 Operate direct channels · 2.2 Develop and manage retail store channel · 2.3 Operate retail store · 2.4 Develop and manage omni channel · 2.5 Manage customer relationship || 3.1 Perform customer and market analysis · 3.2 Market to customers || 4.1 Develop product plan · 4.2 Manage product development lifecycle · 4.3 Source products || 5.1 Operate warehouse · 5.2 Manage transportation and logistics · 5.3 Manage enterprise inventory · 5.4 Manage direct-to-store-delivery || 6.1–6.3 service delivery governance / resources / delivery.

The retail-native content that cross-industry genuinely lacks, with PCF numbers: 2.2.2.2 Design seasonal layouts (planograms) · 2.3.1 Operate customer checkout · 2.3.2.6 Manage store pick-up orders · 2.3.4 Manage store inventory (2.3.4.2 Restock shelves; 2.3.4.3 Monitor and remedy out of stocks) · 2.3.5 Manage store cash · 2.3.6 Plan and manage retail store workforce · 2.3.7 Execute floor merchandising and promotions (2.3.7.2 Maintain shelf tagging) · 2.4.4 Prevent loss (shrink) · 2.4.6 Manage omni-channel experience · 3.2.6 Develop and manage customer loyalty programs · 4.1.1 Develop category plan · 4.1.2 Define assortment plan · 5.3.1 Replenish retail stores · 5.4 Manage direct-to-store-delivery.

The Kwik Trip verdict is a hard one. A case-insensitive grep of the full extracted text for fuel, convenience, c-store, grocery, foodservice, perishable, private label, pharmacy returns zero matches in all 30 pages. (I ran this myself against my own download, independently of the sub-agent that first located the file; matches for "deli" are all substrings of "delivery"/"deliver".) The Retail PCF is a general-merchandise / apparel / omni-channel model built with Microsoft's retail SMEs. It has no process content for fuel retailing, forecourt operations, prepared food/foodservice, fresh and perishable handling, private label manufacturing, or the convenience format. For Kwik Trip, which pumps fuel, runs a commissary and bakery, makes its own dairy, and self-distributes, roughly the entire value-making core of the business is outside this framework's scope. Named plainly: there is no APQC industry PCF for convenience stores, grocery, or fuel retail.

3. Licensing — the one unambiguous good news

Read directly, verbatim from the v7.4 cross-industry PDF, copyright page:

©2024 APQC. ALL RIGHTS RESERVED. The Process Classification Framework is the copyrighted intellectual property of APQC. APQC encourages the wide distribution, discussion, and use of the PCF for classifying and defining organizational processes. Accordingly, APQC hereby grants you a perpetual, worldwide, royalty-free license to use, copy, publish, modify, and create derivative works of the PCF, provided that all copies of the PCF and any derivative works contain the following attribution:

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. The PCF is intended to facilitate organizational improvement through process management and benchmarking, regardless of industry, size, or geography. To download the full PCF or industry-specific versions of the PCF, as well as associated measures and benchmarking, please visit www.apqc.org/pcf.

The Retail PCF v7.2.1 carries a materially identical grant (©2019, opening "This Process Classification Framework® ('PCF') is the copyrighted intellectual property of APQC"). Page footers on both read "Permission granted to photocopy for personal use." — that line sits alongside, and is narrower than, the derivative-works grant on the copyright page; the grant is the operative term.

What this means for a consulting firm, stated carefully. The license text is unqualified as to who may exercise it — no non-commercial carve-out, no consultant exclusion, no field-of-use limit, no fee. Derivative works are expressly permitted. The only stated condition is the attribution paragraph, reproduced in all copies of the PCF and any derivative works. My reading: phData may derive a client-facing taxonomy from the PCF, including in paid engagement deliverables, provided the attribution paragraph rides along on the derivative. That reading is mine, not APQC's — it is an inference from the license text, not a statement APQC makes about consultancies. If the Organizational Platform ships PCF-derived structure to a client, get it past phData legal on the one question the text does not answer: whether attribution must appear on the client deliverable itself or whether crediting it in the platform's own provenance suffices.

Three honest gaps. (a) The PCF is also distributed as Excel, TreePad, and via APQC's benchmarking portal; I could not read APQC's website terms of use — www.apqc.org returns HTTP 403 to every automated fetch I attempted, including with a browser user-agent. A site-wide ToU could impose conditions the PDF does not. (b) The framework is downloadable at no charge per the PDF's own overview ("available for download at no charge at www.apqc.org/pcf"), but whether that requires free account registration I could not verify — the download pages are behind the same 403. (c) The measures and benchmarking data attached to the PCF are an APQC membership product and are not covered by the framework's derivative-works grant as far as I can tell; the grant text names the PCF, not the Open Standards Benchmarking dataset. Do not assume benchmark numbers are free to redistribute. PCF® is a registered trademark of APQC; use the ® on first mention.

Convergences and contradictions

• Convergence. Both PCF and our tree are 13-ish top nodes and both split value-making work from enabling work — PCF's "operating vs management and support," our tree's implicit Sales/Marketing/Service/Operations/Supply Chain vs Finance/HR/IT/Legal split. The coarse shape agrees, which means the disagreements below are about axis, not about resolution.
• Contradiction, and it is the load-bearing one. PCF decomposes by what work is done; our tree decomposes by function, then by the pattern in which that function is run. Field sales vs inside sales vs ecommerce are not three different processes in PCF's sense — they are three operating models for the same process. PCF acknowledges this only once, at 3.5.6 Perform sales at physical outlets (21427), 3.5.7 Perform field sales (21428), 3.5.8 Perform digital sales (21429). I checked: all three are childless leaves at level 3. PCF names our entire motion axis and then declines to decompose it. That is the clearest possible evidence that the two frameworks are orthogonal below the top layer.
• Contradiction. The vault's process worldview ([[2026-04-03-management-is-prediction-spc]]) and PCF both treat the org as a process graph with manipulable inputs. Our tree treats it as a routing surface for use cases and role costs. PCF is far better at the former and structurally unable to serve the latter — process taxonomies have no natural place to hang an SOC code or a loaded rate, because processes are not staffed, seats are.

Synthesis for RDCO

Bottom line: borrow PCF's identifier discipline and its coverage checklist; do not borrow its shape. PCF is the wrong axis for what our tree is for, but it is the best available auditor of whether our tree has holes. Treat it as a completeness oracle and an id-design precedent, not as a source of structure. The license is permissive enough that borrowing is a design question rather than a legal one, which is the unusual and lucky part of this answer.

The mapping table

Our function/motion tree against PCF 7.4 cross-industry (CI) and Retail 7.2.1 (R). "Buries" means PCF has the content but at a depth or under a parent that makes it invisible at our altitude.

Borrow-vs-build verdict, per function

The structural critique — where PCF simply cannot be borrowed

PCF decomposes on process: what is done, in what order, to produce an output. Our tree decomposes on function → motion: who owns a domain, and which operating pattern they run it in. These are orthogonal, and the orthogonality is not a defect in either.

The proof is at CI 3.5.6/3.5.7/3.5.8. APQC put physical outlets, field sales, and digital sales into the framework as three sibling processes — and gave them no children. In a process taxonomy those three are near-identical: qualify, quote, close, book. The differences that matter are cost structure, headcount shape, cycle time, tooling, and who you hire — every one of which is a staffing and economics fact, not a process fact. PCF cannot decompose them because there is nothing process-shaped to decompose. That is exactly the material our motion layer exists to carry, and it is why the motion layer has to be built rather than borrowed. Any attempt to derive our 36 motions from PCF's level 2 will produce a process taxonomy wearing our labels, and the 80 role pages will not hang off it.

The mismatch is superficial, though, wherever a function's work is genuinely one operating pattern. Finance, HR, and Supply Chain are like this: there is no meaningful "field AP" vs "inside AP." For those functions our motions are effectively PCF process groups at lower resolution, and borrowing PCF's boundaries costs nothing and buys coverage. The honest split is: the motion layer is real and un-borrowable in the customer-facing functions (Sales, Marketing, Service, and IT), and is a thin relabeling of process groups in the back-office functions. That asymmetry is itself a finding the platform should state out loud rather than hide behind a uniform-looking tree.

Two things to borrow outright regardless:

1. The dual-identifier scheme. A stable 5-digit concept id decoupled from the positional path, with a new id minted when a definition substantially changes. Our current ids (FN.SALES.INSIDE) are positional and semantic and stable — three jobs one string cannot hold. The moment a motion moves between functions, every client YAML that cites it breaks. PCF solved this in 1992; we should copy the solution before the first re-parenting, not after.
2. The completeness oracle. Run every client's org through the 13 PCF categories as a checklist. If a category has no home in our tree and the client staffs it, that is a coverage gap. For Kwik Trip, that test currently fires on EHS, PMO/change management, government relations, and internal controls.

And one thing to stop expecting: there is no APQC framework for convenience, grocery, or fuel retail. The Retail PCF is a general-merchandise omni-channel model with zero content on forecourt, foodservice, fresh, or private-label manufacturing. Kwik Trip's core value-making work — pump fuel, make food, make dairy, self-distribute — is the part APQC does not cover. Our FN.OPERATIONS.CORE_PRODUCTION motion, defined as "the industry's value-making work," is doing the job PCF's retail cut cannot, and that is a point in favor of the design we already have.

Why this is in the vault

This brief unblocks phase 3 of the Organizational Platform build: the README states the hand-section template locks after the framework-research round, and this is that round for the PCF leg. It settles three concrete build decisions — that the motion layer is built not borrowed, that supply chain and finance boundaries can be lifted from PCF 7.4, and that PCF's stable-concept-id scheme should be adopted before any motion is re-parented — plus one client-facing fact for the Kwik Trip engagement: there is no APQC framework covering convenience, fuel, or grocery operations, so the core-production motion carries that weight alone.

Open follow-ups

• What changed structurally between PCF 7.4 (Aug 2024) and 8.0 (May 2025)? Specifically: did CI 3.5.6/3.5.7/3.5.8 — the channel-motion leaves — gain children in 8.0? If APQC has begun decomposing operating patterns, that reverses this brief's core "orthogonal axes" finding and is worth knowing before the template locks.
• Does APQC's site-wide terms of use impose conditions beyond the PDF's derivative-works grant, and does the free download require account registration? Both are behind the 403 and both change the legal footprint of a client-facing derivative.
• Is there a non-APQC process or capability reference model that does cover convenience-store, fuel-forecourt, and retail-foodservice operations — e.g. from NACS, FMI, Conexxus, or the grocery-industry data standards bodies? If one exists, it fills the exact hole APQC leaves for Kwik Trip.
• PCF puts analytics in two places (CI 8.4 under IT and CI 13.7 as an enterprise capability). Do the other mature process frameworks make the same split, and is there evidence about which placement predicts better analytics outcomes? This bears directly on whether FN.IT.DATA_ANALYTICS is the right home for the motion phData sells into.

Related

Filed the same night, same research round — and they do not fully agree. [[2026-08-17-gtm-motion-origins-industry-reference-models]] · [[2026-08-17-bizbok-operating-model-function-motion-mapping]]. Two disagreements the founder should see before the content template locks. (1) This brief concludes the motion layer is real and un-borrowable in the customer-facing functions including Marketing and IT; the GTM sibling grades Marketing and IT as sub-functions rather than true motions. Opposite verdicts on the same two functions. (2) The GTM sibling proposes an axis: substitutable | sub_function frontmatter amendment; the BIZBOK sibling concludes the founder's original prior survives and proposes a different addition (a configured-as block: location / systems / org shape). Note also that the GTM sibling carries a VERIFICATION STATUS: ITERATE (hard) banner — weigh its verdict accordingly against this one.

• [[2026-08-04-kwik-trip-ai-architecture-engagement-context]] — the live engagement whose convenience/fuel/foodservice shape is the reason the Retail PCF's coverage gap matters.
• [[2026-04-03-management-is-prediction-spc]] — the process-as-manipulable-system worldview that PCF embodies and our function/motion tree deliberately does not.
• [[2026-05-26-moonshots-organizational-singularity-ep258]] — organizations architected around intelligence rather than hierarchy; the axis neither PCF nor our tree currently models.
• [[WRITING-rdco]] — the writing standard applied to the Organizational Intelligence framework set.

Sources

Primary, read directly:

• APQC's Process Classification Framework® — Cross-Industry, Version 7.4 (August 2024), APQC code K014750. Public mirror: https://solutions.ifrc.org/sites/default/files/2024-10/K014750_APQC%20Process%20Classification%20Framework%20(PCF)%20-%20Cross%20Industry%20-%20PDF%20Version%207.4.pdf — full text read; levels graphic read as a rendered page image.
• APQC Retail Process Classification Framework®, Version 7.2.1 (January 2019), APQC code K09368: https://www.apqc.org/system/files/K09368_Retail%20Process_v721_011519.pdf — full text read and independently re-verified (categories, retail-specific nodes, keyword sweep for fuel/convenience/grocery/foodservice).

Secondary, not read directly (apqc.org HTML returns HTTP 403 to automated fetch):

• APQC PCF Cross-Industry PDF Version 8.0 resource listing: https://www.apqc.org/resource-library/resource-listing/apqc-process-classification-framework-pcf-cross-industry-pdf-13 — v8.0 existence and 2025-05-30 release date via search-result page text only.
• APQC PCF cross-industry and industry-specific versions collection: https://www.apqc.org/resource-library/resource-collection/apqcs-process-classification-framework-pcf-cross-industry-and — 403, not read.
• APQC press release, "APQC Releases Retail Process Classification Framework": https://www.apqc.org/about-apqc/news-press-release/apqc-releases-retail-process-classification-framework — November 2012 origin and Microsoft collaboration, via search-result text.
• APQC PCF FAQs: https://www.apqc.org/process-frameworks/pcf-faqs — 403, not read.

Vault:

• rdco-vault/01-projects/phdata/2026-08-04-kwik-trip-ai-architecture-engagement-context.md
• rdco-vault/06-reference/2026-04-03-management-is-prediction-spc.md
• rdco-vault/06-reference/2026-05-26-moonshots-organizational-singularity-ep258.md
• rdco-vault/02-sops/WRITING-rdco.md

Working tree (phData-internal, not published):

• /Users/ray/Documents/phdata-projects/organizational-intelligence/organizational-platform/README.md and the 10 function / 36 motion pages under 01-functions/ and 02-motions/.