Four-Portfolio Archetype Standard — Profile Catalog

Standard: Four-Portfolio Archetype and AI Workforce Operating Standard Catalog version: Candidate 0.1.0 Inventory snapshot: 2026-08-08 — 25 categories, 107 unique implemented leaves Archetype source: packages/storefront-templates/src/archetypes/ at 4b40416fefb787389a06c2afdf252764cfdffc81 Authority boundary: the storefront-template archetype registry owns category and leaf identity; this document is a dated, mechanically checkable profile projection

IT4IT™ is a trademark of The Open Group. The mark is used only for accurate editorial reference to the IT4IT Reference Architecture; no affiliation, endorsement, certification, or trademark license is claimed.

1. Purpose

This catalog makes the core standard recognizable and usable across DPF’s implemented industries without publishing 106 repetitive standards. Each organization composes:

core requirements
  + reusable facet profiles
  + one or more category baselines
  + genuine leaf deltas
  + organization, jurisdiction, contract, and deployment overlays

The catalog is both a communication aid and a conformance target. It says what each archetype profile must cover; it does not claim that today’s implementation already has operational evidence for every field.

2. Facet registry

Facet IDs are stable within the catalog major version. A leaf may select several facets on an axis. Selection never weakens a core requirement.

2.1 Commercial and public-value facets

2.2 Delivery topology facets

2.3 Resource, asset, and custody facets

2.4 Workforce and allocation facets

2.5 Trust and control facets

2.6 DigitalProduct/CSDM deployment facets

3. Shared value-stream overlays

The six-stage macro-backbone remains the default. These overlays express the industry-recognizable differences that should be reused rather than reimplemented per leaf:

4. Category baselines

Each row states the base profile. Leaf deltas in Section 5 refine, but do not replace, it.

5. Leaf-delta register

Each line records the genuine delta the leaf profile must make visible. It is not a substitute for the category baseline or the source archetype definition.

5.1 Healthcare and wellness (9)

• veterinary-clinic — animal patient plus owner/guardian, species/weight/medication context, clinical encounter, welfare and veterinary authority.
• dental-practice — chair/provider capacity, imaging/procedure/treatment plan, sterilization and dentist/hygienist activity boundaries.
• medical-practice — human clinical encounter, diagnosis/treatment/referral boundaries, protected record and urgent escalation.
• physiotherapy — assessed plan of care, repeated sessions, progress/outcome measures, exercise and practitioner scope.
• counselling — confidential sessions, therapeutic plan, crisis/safeguarding escalation, consent and highly sensitive notes.
• optician — examination/prescription plus frames/lenses goods, clinical/retail split, fitting and fulfillment.
• home-health-care — field visits to a residence, care plan, worker/patient safety, schedule and visit verification.
• mobile-phlebotomy — dispatch, patient identity, specimen collection/label/custody/temperature, lab handoff and failed-draw evidence.
• dme-delivery — prescribed/eligible durable medical equipment, owned/serialized goods, delivery, setup/training, service and recovery.

5.2 Beauty and personal care (6)

• hair-salon — chair/stylist schedule, service formula/history, chemical/hygiene controls, retail product add-on.
• barber-shop — walk-in/appointment chair flow, rapid repeat service, hygiene and practitioner availability.
• nail-salon — station/technician schedule, chemical/infection controls and repeated service history.
• beauty-spa — rooms/equipment, multi-service packages, contraindication/consent and treatment boundaries.
• personal-trainer — individual/session/package commitments, facility or field delivery, health context, progress and safety.
• mobile-beauty — provider route, client-site conditions, portable stock/equipment, travel and worker/client safety.

5.3 Trades and maintenance (11)

• facilities-maintenance — multi-site planned/reactive work, asset register, vendor/crew assignment, preventive schedule and service evidence.
• plumber — water/gas/site isolation, parts/fixtures, code/license boundaries, leak/damage evidence.
• electrician — electrical isolation, permit/license, energized-work safety, inspection and test evidence.
• cleaning-service — recurring site schedule, crew, chemicals/equipment, access/security, checklist and quality inspection.
• landscaping — route/crew/equipment, seasonal plan, weather, property access and pesticide/safety overlays.
• hvac-contractor — skill/parts dispatch, refrigerant/environmental license, readings, repair/test, maintenance agreement.
• pest-control — site/pest diagnosis, regulated chemical selection/application, occupant/pet risk, notice and follow-up.
• appliance-repair — appliance/model/part fit, technician dispatch, electrical/gas safety, warranty and repair verification.
• pool-spa-service — recurring route, chemistry readings, chemical stock, site access, water/safety controls.
• pressure-washing — site/material assessment, water/chemical/environmental controls, equipment and damage prevention.
• roofing-gutters — estimate/project plus crew/material delivery, weather, fall protection, inspection and warranty.

5.4 Professional services (8)

• it-managed-services — client-estate isolation, recurring service commitments, alerts/incidents, privileged access, change and vendor dependencies.
• legal-services — matter/client/conflict, privilege, jurisdiction/advice boundary, deadlines, review/filing authority and evidence.
• accounting — engagement/period close, source records, reconciliation, tax/advice boundaries, approval and retention.
• marketing-agency — campaign/project, brand and audience context, content approval, channel rights, performance and spend evidence.
• consulting — qualify/scope, milestone deliverables, analysis/recommendation boundaries, client acceptance and knowledge transfer.
• field-inspection — inspector credential, site dispatch, checklist/observation, geospatial/photo evidence and finding escalation.
• land-surveying — licensed survey scope, field crew/equipment, control points, legal descriptions, precision and signed deliverable.
• process-serving-notary — identity/jurisdiction, document custody, attempt/event evidence, notarization/service authority and affidavit.

5.5 Software platform (1)

• software-platform — DigitalProduct/Product alignment, tenant/entitlement, version/release/service instance, support, telemetry, security, privacy and renewal.

5.6 Education and training (4)

• corporate-training — client/cohort engagement, curriculum/version, instructor, completion and organization outcome reporting.
• tutoring — learner/guardian, subject/level, recurring session, progress, safeguarding and scheduling.
• music-school — instructor/room/instrument, individual and class patterns, recital/performance and progression.
• driving-school — licensed instructor/vehicle, road lesson route, learner eligibility, vehicle and public safety, assessment evidence.

5.7 Pet services (5)

• pet-grooming — animal/owner record, appointment, grooming instructions, welfare, condition and handback.
• dog-walking — recurring/mobile schedule, key/access custody, route, animal grouping and incident evidence.
• pet-boarding — date-range occupancy, kennel/room, feeding/medication, owner instructions, welfare and return.
• mobile-pet-grooming — vehicle/route, animal appointment, water/equipment/stock, site safety and welfare.
• mobile-vet — veterinary clinical authority plus field dispatch, controlled supplies/specimens, urgent escalation and records.

5.8 Food and hospitality (3)

• restaurant — reservations/walk-in tables, POS, menu/recipe, kitchen/crew/perishable stock, allergen/sanitation and service recovery.
• catering — quote/project, event date/venue/guest count, production/logistics/crew, food safety and event acceptance.
• bakery — recipe/batch production, preorder/POS, perishable ingredients, allergen/label and pickup or delivery promise.

5.9 Retail goods (5)

• retail-goods — owned stock, store/online order, payment, fulfillment, return and supplier/product trace.
• artisan-goods — made-to-stock/made-to-order goods, craft production, customization, lead time and provenance.
• florist — perishable inventory, arrangement production, occasion/date, route delivery and substitution approval.
• wholesale-distribution — account/pricing/credit, bulk order, warehouse/pick/ship, supplier and trade commitment.
• furniture-delivery-install — bulky serialized goods, route/crew, site access, installation, condition/damage and customer acceptance.

5.10 Fitness and recreation (3)

• gym — membership/entitlement, facility/equipment access, capacity, safety, class/PT add-ons and renewal.
• yoga-studio — membership/class pass, instructor/room capacity, ability/health context, safeguarding and attendance.
• dance-studio — learner/guardian, classes/levels, instructors/rooms, performance/recital and safeguarding.

5.11 Nonprofit and community (8)

• pet-rescue — animal intake/custody, foster/adoption, donations, volunteer capacity, welfare and adopter suitability.
• animal-shelter — public/contract intake, occupancy, care, reclaim/adoption, medical/welfare and records.
• community-shelter — bed/room capacity, beneficiary intake/eligibility, safeguarding, services, privacy and exit planning.
• charity — donor restriction/receipt, campaign, program allocation, beneficiary outcome and public/donor reporting.
• sports-club — membership, teams/fixtures/facilities, coaches/volunteers, safeguarding and member governance.
• cooperative — member ownership, equitable access/allocation, contribution, governance, surplus and conflicts.
• agricultural-cooperative — member/co-op governance plus pooled inputs/equipment/market access, seasonal capacity and traceability.
• meal-delivery-program — beneficiary eligibility, donation/grant funding, meal production, diet/allergen, route/proof and safeguarding.

5.12 HOA and property management (3)

• homeowners-association — owners/board, dues, covenants, amenities, requests/violations, vendor work and member governance.
• condo-association — unit/common-element distinction, board/owner duties, shared systems, assessment/dues and access.
• property-management-company — landlord/client portfolio, tenants/leases, maintenance/vendors, rent/accounting and dual-party authority.

5.13 Banking and financial services (3)

• community-bank — deposit/account and loan relationships, branch/community channel, KYC, credit decision, servicing and regulatory evidence.
• credit-union — member eligibility/ownership, deposit/loan services, equitable member governance, KYC and regulation.
• mortgage-lending — application/disclosures, verification, underwriting, appraisal/title, approval/adverse action, closing and servicing handoff.

5.14 Public sector (3)

• small-town-municipality — resident requests, permits/fees, public meetings/records, public works, fairness and statutory authority.
• municipal-utility — service territory/account, meter/usage, connect/disconnect, outage/field work, infrastructure and universal-service controls.
• law-enforcement-agency — call/incident/case/evidence, dispatch/officer activity, public-safety authority, due process, CJIS/records and critical escalation.

5.15 Asset rental (3)

• equipment-rental — asset availability, reservation, identity/deposit, checkout, condition, return/inspect, damage and maintenance.
• self-storage — unit availability/access, agreement/recurring payment, customer custody, facility security and delinquency/legal boundary.
• production-equipment-rental — specialized equipment packages, availability, logistics/setup, condition/maintenance, operator/safety and return.

5.16 Real estate and construction (2)

• new-home-builder — model/community sales, selection/design, standardized build plan, jobsite, inspections/draws, handover and warranty.
• custom-home-builder — client-specific design/allowances/change, contract, subcontractors, materials, milestone acceptance and warranty.

5.17 Automotive services (6)

• auto-glass — VIN/glass/ADAS fit, mobile dispatch, removal/install, calibration, safety and insurance/acceptance.
• mobile-mechanic — vehicle symptom/part/skill match, site dispatch, diagnose/approve/repair/test and roadside/site safety.
• mobile-detailing — route/site, package, water/power/chemicals, vehicle condition, service and damage prevention.
• mobile-tire — tire/vehicle fit, mobile stock, dispatch, roadside lifting/safety, install/torque evidence.
• roadside-assistance — urgent location/vehicle triage, dispatch, towing/service authority, public road safety and proof.
• locksmith — identity/ownership authorization, key/access security, dispatch, bonding/license and incident evidence.

5.18 Moving and logistics (5)

• moving-company — survey/estimate, crew/truck, item inventory/custody, load/route/unload, damage and acceptance.
• junk-removal — estimate, crew/vehicle, custody/ownership, sort/disposal/donation manifests and site safety.
• courier-delivery — parcel identity, pickup/custody, route, delivery attempt/proof, exception and loss.
• last-mile-freight — shipment/pallet, dock/appointment, vehicle/crew, route, delivery/condition and carrier evidence.
• freight-brokerage — shipper/carrier contract, capacity sourcing, tender, tracking, documentation, settlement and no implied physical custody.

5.19 Security services (2)

• guard-patrol — licensed guard, site/post orders, roster/route, incident/escalation, presence and evidence.
• alarm-cctv-install — survey/design, equipment/technician, install/configure/test, privacy, monitoring handoff and maintenance.

5.20 Media production (3)

• film-video-production — brief/script/rights, cast/crew/location/equipment, shoot, review/version, delivery and safety.
• post-production-studio — media custody, edit/VFX/audio workflow, suite/artist capacity, review/version, rights and secure delivery.
• event-production-staging — show design, equipment/crew/logistics, build/rehearse/live/strike, venue coordination and safety.

5.21 Live events and venues (3)

• event-venue — date/space hold, capacity/package/contract, setup/event/strike, accessibility, safety and settlement.
• tour-promoter — show/tour plan, venue/talent contracts, marketing/ticketing, production, settlements and rights.
• talent-booking-agency — buyer/talent fit, availability/hold, negotiation/contract, itinerary, performance and commission settlement.

5.22 Warehousing and fulfilment (4)

• third-party-logistics — client/account, dock/receive/store/pick/ship, client inventory custody, meter/SLA and carrier integrations.
• ecommerce-fulfilment — order ingestion, inventory allocation, pick/pack/label, carrier handoff, returns and merchant evidence.
• cold-chain-storage — temperature-zone capacity, monitored lot custody, excursion response, traceability and validated handoff.
• cross-dock-transload — inbound/outbound appointment, dock/door/equipment, rapid custody transfer, count/condition and reconciliation.

5.23 Fabric care services (3)

• dry-cleaning-plant-network — store/route/plant custody chain, garment/care label, batch/chemical process, ready promise, damage and environmental controls.
• wash-and-fold-laundry — weight/bag/customer custody, wash/dry/fold, route/pickup, ready promise and loss/damage evidence.
• alterations-tailoring — garment custody, measurements/fitting, scoped alteration, skilled labor, approval, completion and fit evidence.

5.24 Agriculture and ranching (3)

• mixed-farm-ranch — whole-operation coordination across land, forage/crops, cattle, working animals, equipment, inputs, outside providers and several seasonal horizons.
• crop-hay-farm — field/stand and fertility readiness, weather and pest evidence, regulated inputs, equipment/custom-operator dependencies, harvest windows, quality/lots and storage.
• cattle-ranch — herd/group and individual identity, breeding/calving, health/treatment/withdrawal, movement, forage/water, working-animal support and evidence-bounded market readiness.

5.25 Manufacturing (1)

• industrial-equipment-oem — configured and standard equipment, engineering release, material and production readiness, routed work, inspection/test, serialized delivery, spares and lifecycle support; operational visibility never implies PLC, robot, safety-system, or machine-control authority.

6. Shared and specialized AI-coworker families

The unit of reuse is a stable DigitalProduct/profile-family activity/authority/evidence contract, not a generic persona label. Every CW-* key in this catalog identifies a design/profile family. It is never a GAID AgentSubject ID, a deployed coworker, or evidence that an implementation exists. GAID alone governs subject identity creation and lifecycle.

Each row below is a stable family identifier and design skeleton, not a complete Profile. To bind a family means resolve that key to a separately versioned Profile satisfying FPAW-PROF-001 and FPAW-CAT-006, including its exact activities, authority ceiling, evidence contract, owner, and effective period. The table row alone cannot satisfy a coworker claim.

Candidate specialized families include:

• CW-CLINICAL-COORDINATION for clinical workflow boundaries without autonomous diagnosis by default
• CW-FINANCIAL-REGULATORY for KYC, credit/model-risk, disclosure, and adverse-action evidence
• CW-CIVIC-PUBLIC-SAFETY for due process, public records, emergency priority, and state authority
• CW-CUSTODY for ownership, possession, item/lot identity, condition, transfer, discrepancy, and handoff
• CW-COLD-CHAIN, specializing CW-CUSTODY, for temperature, excursion, release, and regulated handoff
• CW-LICENSED-CRAFT for trade/site/license/safety/inspection boundaries
• CW-PROFESSIONAL-ADVICE only where the profession, jurisdiction, qualification, authority, and relying-party evidence justify a distinct DigitalProduct/profile family
• CW-AGRICULTURAL-OPERATIONS for the seasonal, biological, geographic whole-operation loop across land, crops/forage, animals, equipment, materials, outside services and cited external signals

6.1 Controlled activity-applicability and AI-realization states

The category matrix uses exactly four activity-applicability states. It says whether the business activity and a reusable design boundary are material; it does not require an organization to deploy AI or assert that a production coworker exists.

Every non-not-applicable cell is resolved separately through exactly one AI-realization state:

required never grants decision authority or makes AI preferable to human work. human-only in the core allocation vocabulary remains a valid target realization. When profile-bound is selected, the profile may still constrain the coworker to retrieval, recommendation, drafting, or routing. specialized-profile-required never implies autonomous execution: its profile must state the TAK ceiling, human handoff, prohibited actions, and evidence contract.

6.2 Category applicability matrix

The following is one logical matrix, with one row for each canonical category and one column for each reusable shared family defined above. Column keys are aliases only; the family IDs remain the authoritative identifiers.

6.3 Activity, authority, and evidence rationale

This rationale is the minimum category-level reason for the matrix state. A specialized profile may derive from a candidate family listed above or from the affected shared family, but it must remain a versioned category/leaf contract rather than an ungoverned persona prompt.

6.4 Leaf deviations

The matrix is inherited unchanged unless Section 5 identifies a leaf semantic that adds an activity or raises its authority/evidence boundary. A deviation record MUST name the family, inherited and leaf states, activity trigger, authority ceiling, evidence, reviewer, and profile version. A leaf may tighten recommended or required to specialized-profile-required. It may lift not-applicable only from explicit source semantics. A relaxation requires scope-specific contrary evidence and is not predeclared by this catalog.

The following deviations are the only leaf differences established by the current catalog evidence. Each row contains exactly one leaf/family pair so the inherited and resulting states are machine-checkable:

Every row inherits profileVersion = 0.1.0, reviewer = DPF-FPAW candidate editorial review, and reviewedAt = 2026-08-01. It also inherits sourceEvidence = the canonical ALL_ARCHETYPES record for the named leaf plus its Section 5 delta, derivationMethod = editorial semantic projection, confidence = provisional, and EvidenceVerificationStatus = provisional; this is design evidence, not proof of implementation. Its authority ceiling is determined by the resulting state: specialized-profile-required means no-execution-until-specialized-profile; required or recommended means no-execution-until-complete-organization-profile. These inherited fields are part of each deviation record, not optional commentary.

An archetype profile MUST NOT claim a shared coworker merely because a seed exists. It must bind the coworker to activities, job/skill requirements, authority, tools/data, controls, handoffs, evaluation, and evidence.

7. Profile manifest contract

The following YAML is a partial, non-conformant syntax excerpt that demonstrates the archetype and binding portions of the logical contract. It is not a new authoritative registry, a commitment to YAML persistence, or a complete Profile under FPAW-PROF-001. A conforming manifest must additionally resolve purpose, applicability, exact requirement membership, vocabulary and mapping records, owner, effective period, verifier, and every assertion in Section 7.1.

profile:
  id: fpaw:leaf:hvac-contractor
  version: 0.1.0
  standard: DPF-FPAW@0.1.0
  sourceArchetype:
    id: hvac-contractor
    category: trades-maintenance
    inventorySnapshot: 2026-08-01
  inherits:
    - fpaw:category:trades-maintenance@0.1.0
    - OVL-FIELD-DISPATCH@0.1.0
  facets:
    commercial: [COM-TRANSACTION, COM-RECURRING, COM-HYBRID]
    delivery: [DEL-FIELD]
    resources: [RES-PEOPLE-TIME, RES-FLEET, RES-OWNED-STOCK, RES-REGULATED-RECORD]
    workforce: [WRK-HUMAN-LED, WRK-AUGMENTED, WRK-AI-PRIMARY]
    trust: [TRU-PRIVACY, TRU-PROFESSIONAL, TRU-SAFETY, TRU-ENVIRONMENT]
    digital: [DIG-PLATFORM-HOSTED, DIG-EDGE, DIG-HYBRID-AI]
  businessProducts:
    forms: [service, good, hybrid]
    examples: [repair visit, maintenance agreement, replacement part]
  portfolioAspects:
    products_and_services_sold: [repair and maintenance offers, parts sold]
    for_employees: [technicians, dispatcher coworker, contributor tools]
    manufacturing_and_delivery: [dispatch operation, vans, gauges, truck stock]
    foundational: [identity, finance, data, communications, model gateway]
  valueStream:
    base: [attract, capture, qualify, deliver, settle, retain]
    overlays: [triage, assign-dispatch, en-route, onsite, repair-test-close]
  aiRealizationDecisions:
    - family: CW-SCHEDULE-DISPATCH
      state: implementation-gap
      intendedProfile: CW-LICENSED-CRAFT/hvac-dispatch@0.1.0
      gapReason: no separately published versioned specialized Profile is bound
    - family: CW-PROFESSIONAL-ADVICE
      state: human-only-no-ai-needed
      rationale: regulated diagnosis and authorization remain qualified-human work in this profile
  workAllocation:
    - activity: rank-dispatch-options
      pattern: ai-primary-human-exception
    - activity: diagnose-refrigerant-system
      pattern: human-led-ai-assisted
    - activity: authorize-regulated-work
      pattern: human-only
  physicalWork:
    location: customer-site
    requires: [licensed-technician, equipment, materials, safe-state, readings, inspection]
  digitalBindings: []
  digitalBindingVerification:
    bindingState: absent
    evidenceVerificationStatus: unverified
    gap:
      id: GAP-HVAC-DIGITAL-BINDINGS
      summary: no DigitalProduct lifecycle or deployment binding is verified for this illustration
      evidenceNeeded: [owned DigitalProduct identity, lifecycle touchpoint, deployment relationship, reviewer]
  evidence:
    provenance: explicit
    readiness: template-ready
    lastReviewed: 2026-08-01

7.1 Required manifest assertions

For every leaf, the conformance check MUST assert:

1. the source leaf exists exactly once in the canonical registry
2. exactly one category baseline is inherited
3. Product forms and outcomes are declared
4. every portfolio root has governed aspects or justified non-applicability
5. the ValueStream and overlays satisfy the Stage contract to claimed depth
6. WorkUnitDefinitions and allocations reference jobs/skills/qualifications or explicit Gaps
7. physicality, location, resources, materials, custody, and completion evidence are declared
8. controls and outcome/flow/quality/economic/capacity/risk measures are declared
9. DigitalProduct lifecycle/external-standard bindings are explicit or absent—not defaulted
10. provenance, implementation state, readiness, reviewer, and date are present

7.2 Catalog requirement register

These namespaced requirements index every normative obligation introduced by this catalog. They are selected by an FPAW-Industry-Archetype claim that cites Catalog Candidate 0.1.0.

7.3 Worked profile-composition specimens (informative)

These seven specimens exercise six materially different design shapes plus agriculture. They are not complete Profiles, leaf manifests, implementations, or ConformanceClaims: they summarize composition intent while deliberately omitting the per-stage contract, complete WorkUnit/job/skill/ qualification/evidence graph, organization thresholds, and all ten family-cell decisions required by Sections 6–7.2. A family key below remains a design skeleton; every intended AI participation is therefore implementation-gap until a separately published, versioned Profile and deployment overlay satisfy FPAW-PROF-001, FPAW-CAT-003, and FPAW-CAT-006.

For comparison, each specimen uses the same design metadata: Candidate 0.1.0 Core, Four-Portfolio, Business-Offering-Value, Operational-Work, Workforce-AI, Industry-Archetype, and Assurance-Evidence; FPAW vocabulary and canonical DPF Stage keys; prospective owner DPF Standards Steward; design date 2026-08-01; review-on-source-change; external BindingState absent; ImplementationState = defined; readiness = template-ready; and EvidenceVerificationStatus = provisional. These are informative design defaults, not normative profile fields or evidence of completeness.

FPAW-EX-HVAC-CONTRACTOR@0.1.0 — physical/licensed service

FPAW-EX-COMMUNITY-BANK@0.1.0 — regulated decision work

FPAW-EX-FURNITURE-DELIVERY-INSTALL@0.1.0 — physical goods plus service

FPAW-EX-THIRD-PARTY-LOGISTICS@0.1.0 — custody/logistics

FPAW-EX-SMALL-TOWN-MUNICIPALITY@0.1.0 — public/member value

FPAW-EX-SOFTWARE-PLATFORM@0.1.0 — wholly digital Product

FPAW-EX-MIXED-FARM-RANCH@0.1.0 — seasonal biological/physical work

8. CSDM 5 and AI DigitalProduct application boundary

The specimens above remain vendor-neutral applications of DPF-owned product, deployment, service, work, TAK, GAID, and TAK-JSI semantics. The source-validated CSDM 5 map is centralized in the core standard’s Section 13.4; catalog specimens MUST NOT create a second mapping registry.

A ServiceNow implementation profile may project Product Model, Business Application/design, SDLC or AI Digital Assets, runtime CIs/Service Instances, services, Service Offerings, catalog and consumption records to the core levels. It MUST preserve the verified gaps: CSDM 5 does not supply FPAW’s DigitalProductRelease authority, a stable concrete DeploymentPackage class/identity contract, DeploymentIntent, attributable Deployment occurrence, enduring GAID AgentSubject, AIProductOperatingBinding, atomic work allocation, or attributable evidence contract. The supplied AICT publication adds a logical Package (Artifact) layer and a source 1:m:n AI Digital Asset-to-package-to-operational-deployment pattern; this closes the conceptual package-layer gap but does not establish a CSDM table, immutable digest, target-compatibility, provenance, rollback, desired configuration, or deployment-occurrence contract. Physical bindings also MUST carry the applicable ServiceNow family/release, plugins, dictionary/table and relationship fingerprints; source labels alone are not implementation evidence.

9. Current DPF coverage baseline

The baseline is intentionally multi-dimensional. It must not be summarized as “107 archetypes complete.”

9.1 Highest-priority cross-catalog gaps

1. complete Product forms/mixes and four-portfolio placement for every leaf
2. remove legacy IT4IT fallback and create explicit DigitalProduct bindings
3. add activity/job/skill/allocation and physical work to the Stage contract
4. materialize Section 6 bindings and create specialized profiles only at genuine authority/safety/evidence boundaries
5. configure dispatch, trust, custody, supply/material, and metrics facets from evidence
6. join human and AI capacity through Principal-based allocation without erasing employment, qualification, or asset distinctions
7. turn readiness into evidence-backed implementation state rather than template presence

10. Application sequence

For one organization or new archetype:

1. Resolve the current canonical category/leaf composition and Product lines.
2. Classify business Product forms and intended stakeholder Outcomes.
3. Place governed aspects in all four portfolios and type their dependencies.
4. Select the category baseline and reusable commercial/delivery/resource/trust/digital facets.
5. Add genuine leaf, organization, jurisdiction, contract, and deployment deltas.
6. Refine the business ValueStream and complete every material Stage contract.
7. Define WorkUnitDefinitions, jobs/roles/skills, physical requirements, capacity, and allocation.
8. Bind AI coworkers to DigitalProduct lifecycle plus GAID/TAK-JSI/TAK performer controls.
9. Add explicit IT4IT mappings only for evidenced DigitalProduct touchpoints.
10. Record ConformanceClaims and Gaps; route remediation to one primary portfolio and canonical backlog work.

Appendix A — Inventory integrity statement

The 106 leaf IDs in Section 5 are a dated projection of packages/storefront-templates/src/archetypes/index.ts. A verification tool should compare the set of backticked leaf keys in this catalog with ALL_ARCHETYPES, require equal cardinality and membership, and fail when either side contains an unmatched key. The source registry always wins.

Appendix B — Proposed future machine-readable registries

After the candidate standard is reviewed, DPF may project—not duplicate—the following versioned registries from existing substrate:

• ProfileFacetDefinition
• ArchetypeProfileComposition
• StageContractProjection
• WorkUnitDefinition
• WorkAllocationPolicy
• StandardConceptMapping
• ConformanceImplementationStatement

No new table is implied. The schema audit and first consumer workflow determine whether each becomes a relational entity, governed JSON, EA element, generated artifact, or view over current records.