Part I — Enter and characterize the inquiry

DOCA.1 - Bound the Development-Opportunity Inquiry

Type: DPF pattern

Status: Released; evolving

Normativity: Normative unless marked informative.

DOCA.1:0 - Use This When

What is the smallest useful inquiry when someone says “we should develop,” names a fashionable solution, or asks what to develop next before the receiving change is clear?

Use this pattern when a person, organization, community, AI arrangement, platform, facility, research programme, or another identified subject has a development concern or aspiration but the receiving use, horizon, protected conditions, reason to explore, or affordable inquiry effort is still loose. The first useful result is a bounded inquiry that another person can inspect, or one exact missing premise that prevents such an inquiry.

Begin here without appointing an adviser. A person can bound a self-inquiry and continue into opportunity construction. When a distinct performer is already being asked to advise a named recipient, this pattern can recover the subject, use, and horizon, but DOCA.7 governs whether the advising relationship itself is admissible.

Cheap exit. Reuse an existing inquiry when it already identifies the same subject, receiving use, horizon, protections, posture, and effort boundary and no material premise changed. If a qualified domain practice owns the whole question, use it directly. If adequate alternatives already exist and the remaining need is comparison, recommendation, or authorized choice, stop opportunity construction and use the direct decision-support owner.

Ordinary non-use boundary. A research account of change in a non-cultural population or lineage is not advice to that population. A separately authorized researcher may have an opportunity or decision question, but the researcher or sponsoring organization—not the population—then supplies the recipient and authority boundary.

DOCA.1:1 - Problem Frame

A broad wish such as “develop in AI,” “become more mature,” “modernize the platform,” or “build a learning culture” can point to several different subjects and receiving uses. It may concern a person’s capability for later Work, an organization’s contribution and arrangement, an engineered system’s service, an episteme or problem formulation, a research programme, or a proposed intervention. The same words do not make those subjects develop in the same way.

The practical danger appears before alternatives or advice. A course, tool, reorganization, model, supplier, or PatternID can become the answer before anyone names the receiver, useful difference, protected conditions, or evidence needed. The opposite failure is an unlimited discovery exercise whose growing list never returns a result that can be tested or used.

This pattern governs the inquiry boundary: the identified subject, receiving use, declared horizon, protected conditions, reason to explore, posture, inquiry budget, and first missing result. It does not establish a worthwhile problem, qualified opportunity, recommendation, choice, programme, Guide, performed Work, or observed development effect.

DOCA.1:2 - Problem

Without an explicit inquiry boundary:

• a solution label substitutes for the receiving contribution;
• “development” silently shifts among person, organization, technology, knowledge, and population meanings;
• a supplier’s promise is treated as the receiver’s problem;
• the horizon expands or contracts to make a favored direction look plausible;
• safety, workload, continuity, privacy, reversibility, or another protected condition appears only after a candidate has gained momentum;
• search effort grows without a proportional stopping reason; and
• missing authority or evidence is hidden by a polished opportunity statement.

The reader then cannot tell whether to characterize the subject, search neighboring possibilities, request a direct specialist result, bound an advising relationship, or stop.

DOCA.1:3 - Forces

DOCA.1:4 - Solution

Construct the smallest inquiry boundary that can direct one useful next action and expose one truthful stopping point.

DOCA.1:4.1 - Identify the subject and claim posture

Name what may develop or be changed at the grain that matters now: a particular person, organization, community arrangement, AI model-and-scaffold configuration, facility, platform, research programme, episteme, or another exact subject. If identification is provisional, state the candidate boundary and what would settle it.

Mark the claim posture. A proposed future contribution is not actual change. A plan is not performed Work. A model prediction is not an observed result. If development or evolution still hides the subject, continuity rule, or value claim, use E.10.DEV and return with the direct subject owner.

DOCA.1:4.2 - Identify a receiving use or an exploratory question

For a proposed contribution, state who or what could use it, in which situation, and what practical difference would matter. The receiving use may be the subject’s later Work, a service used by another System, an organization’s market or operating contribution, a research use, or a decision that consumes a qualified opportunity.

Keep the receiver’s useful difference separate from the subject’s desired learning, prestige, procurement, technology adoption, or internal activity. If no receiver or receiving situation can yet be named, keep that question open rather than inventing demand.

An inquiry can still start from material that someone can use or change: permitted records, a working procedure, a model or another construction. Name an available operation and a difference worth examining within the inquiry’s resources and permissions. C.40 supplies that development Method. Its result can suggest a receiving use for DOCA.2 or DOCA.3 to investigate. A useful local result can also finish the inquiry; it need not become a development opportunity.

DOCA.1:4.3 - Fix the horizon and protected conditions

Choose a horizon set only as finely as it can change the inquiry. A four-month inquiry may use several sub-horizons; another case may need one decision deadline and one longer consequence horizon. No universal near/middle/far sequence is implied.

Name conditions that the inquiry may not silently trade away. Depending on the subject and use, these can include safety, legal or professional limits, privacy, confidentiality, workload, service continuity, accessibility, resource ceilings, reversibility, distributional consequences, or preservation of future options. The direct practice owns their meaning and evidence.

DOCA.1:4.4 - State the reason to explore and separate its status

Write why exploration is warranted now. Distinguish:

• a qualified receiving problem or demand;
• an observed dissatisfaction or changed constraint;
• a proposed contribution or explicit problem hypothesis;
• a supplier promise, technology signal, or PatternID used only as a search lead; and
• curiosity that is valuable only if a bounded inquiry can be afforded.

Preserve competing formulations when they would send the inquiry toward different contributions. Use the direct problem-structuring pattern when deciding among those formulations is itself the current Work.

DOCA.1:4.5 - Set a proportional inquiry budget and permissions

Declare the effort, elapsed time, people, source access, conversations, computation, and other resources available for this inquiry. State the consequence level that would require stronger evidence before a later commitment.

Permission to inspect a source, interview a participant, or run a desk study does not authorize an intervention, access to restricted records, procurement, advice, or implementation. When the inquiry itself lacks permission, return the exact access or authority gap.

DOCA.1:4.6 - Select the first missing result

Ask which result would most change useful progress at the declared effort:

• a development-facing characterization from DOCA.1.CHR;
• materially different search leads from DOCA.2;
• a worthwhile problem and proposed contribution from DOCA.3;
• an admissible advising question or blocker from DOCA.7;
• a qualified result from a holder, evidence, safety, legal, professional, engineering, organization, operations, strategy, research, or other direct owner; or
• an honest stop because the existing opportunity or option set is already sufficient.

Start there. Publication order does not require all earlier PatternIDs to be used, and using this pattern does not create a lifecycle.

DOCA.1:4.7 - Return the bounded inquiry or exact gap

Use ordinary prose first. The following compact form can support a handoff when several people must inspect the same boundary:

BoundedDevelopmentOpportunityInquiry@Context:
  subjectAndBoundary:
  claimPosture:
  receivingUseAndReceiver:
  horizonSetAndDecisionWindow:
  protectedConditions:
  reasonToExploreAndStatus:
  knownPremises:
  suggestedButUnqualifiedPremises:
  inquiryBudgetAndPermissions:
  firstMissingResult:
  directOwnerOrNextPattern:
  stopOrReopenCondition:

This is a local working form, not a new root kind, WorkPlan, engagement, recommendation, or authorization. An unsettled future receiver can remain unknown while the local question guides the inquiry. Omit a field only when it cannot change the next action and that omission is apparent from the case.

A complete return can be modest: “For engineer-manager Mira’s incident-review contribution during the next four months, explore ways to reduce delayed handoff detection while preserving current service workload and confidential records. Spend up to six hours on characterization and source checks; first obtain the current and intended review characteristics. Stop before course selection or advice.”

DOCA.1:4.8 - Stop, reuse, and reopen locally

Stop when the bounded inquiry identifies a useful next result and its owner, when a truthful blocker prevents that result, or when the existing result is already sufficient for the receiving use. Do not widen merely to increase idea count.

Reopen only the affected boundary when the subject, receiver, receiving use, horizon, protected condition, posture, authority, source premise, or effort budget changes. A changed characteristic need not erase an otherwise usable inquiry; a changed receiving use may.

DOCA.1:4.9 - What changes in practice

Instead of starting with a course, tool, provider, maturity label, or long opportunity list, the practitioner can now say what is being explored and why, over what horizon, under which protections, at what cost, and which result is needed next. A proposed contribution also needs its prospective receiving use. That is enough to begin responsibly without pretending that a recommendation or choice already exists.

DOCA.1:5 - Archetypal Grounding

DOCA.1:5.1 - Person entering construction without an adviser

Mira manages an engineering team and says, “I should develop in AI this quarter.” The phrase does not yet name a receiving contribution. She identifies the subject as herself in her current engineer-manager configuration, the receiving use as improving incident-review and handoff Work over four months, and the receiver as her team and service organization. She protects current service workload, confidential incident data, and her ability to continue the existing role.

She allows six hours for an initial inquiry using current Work examples, two conversations, and qualified source checks. “AI” remains a search seed, not the result. The first missing result is a characterization of review quality, latency, explanation burden, and protected workload under DOCA.1.CHR. She can stop with that bounded inquiry without appointing an adviser or selecting a course.

DOCA.1:5.2 - Organization with a fashionable solution

An engineering company announces that it should “become platform-led.” The inquiry identifies the organization and a specific product-development arrangement, the receiving use as faster and more reliable product-family delivery, a twelve-month horizon with two decision windows, and protected safety, customer continuity, regulatory obligations, and scarce specialist attention.

The provider proposal is recorded as a suggested premise. Strategy owns any commitment, organization-change practice owns changed arrangements, systems and platform engineering own enabling-system realization, and operations owns continuing service. The first missing result is not a platform purchase decision; it is the development-facing characterization that can distinguish materially different contributions.

DOCA.1:5.3 - Advice can enter elsewhere

A committee already has three qualified development directions for an identified facility, a complete characterization, and a current joint-reachability account. Its current need is an independent recommendation. Repeating DOCA.1 adds no value. The adviser begins with DOCA.7 to establish recipient, mandate, competence, conflicts, disclosure, and reliance, then uses current decision-support results. The committee retains the choice.

DOCA.1:5.4 - Population anti-case

A researcher asks, “What should this non-cultural lineage develop next?” No population-local recipient or choice owner is identified. This pattern does not manufacture one. Evolutionary description remains with the applicable domain owner. If the researcher is instead deciding whether to fund an experiment, the researcher or sponsor becomes the decision recipient and a separately bounded research opportunity or decision inquiry can begin.

DOCA.1:6 - Bias-Annotation

• Solution-first bias: familiar technologies and providers can appear more concrete than the receiving use. Keep them as leads until a contribution is qualified.
• Human-development default: do not transfer learning, career, or capability mechanisms to organizations, AI arrangements, engineered systems, epistemes, or populations.
• Sponsor-recipient collapse: the funder, subject, receiver, adviser, and later choice owner may coincide, but name distinctions only when their difference changes protection, disclosure, authority, or use.
• Open-search prestige: a larger idea list can look more rigorous while avoiding the first discriminating question.
• Benefit-by-word bias: development, progress, and maturity establish no beneficial direction without characteristics, polarity, and evidence.
• Form bias: a completed record cannot compensate for an unidentified subject or the absence of a useful question.

DOCA.1:7 - Conformance Checklist

A conforming use or companion account:

1. MUST name the exact subject or provisional subject boundary and claim posture.
2. MUST state the receiving use and receiver when known. Otherwise, identify the local question being investigated and keep the future receiving use open.
3. MUST declare the horizon set or decision window that can change the result.
4. MUST expose protected conditions before candidate selection.
5. MUST distinguish qualified grounds, explicit hypotheses, supplier promises, and search leads.
6. MUST state a proportional inquiry budget and any permission needed for the inquiry itself.
7. MUST identify the first missing result, its direct owner or next pattern, and the smallest useful return.
8. MUST NOT present the inquiry as a recommendation, choice, programme, Guide, performed Work, observed effect, or intervention authority.
9. MUST preserve independent Construction and Advising entry; no PatternID order may be presented as a mandatory lifecycle.
10. MUST state a stop or local reopen condition.
11. SHOULD use ordinary prose before any compact form.
12. MUST return a specific gap or non-use case when the subject or a condition needed for the proposed inquiry cannot be established.

DOCA.1:8 - Common Anti-Patterns and How to Avoid Them

DOCA.1:9 - Consequences

The inquiry becomes cheap enough to start and strong enough to direct a useful next move. A person can explore without inventing an adviser; an adviser can reuse an adequate boundary without forcing construction; and a missing premise becomes a named request rather than hidden uncertainty.

The cost is explicit incompleteness. The result may be only a question, blocker, or narrow source request. Naming the subject, horizon, protections, posture, and budget also makes attractive but unsupported directions visibly weaker. That is preferable to premature certainty.

This pattern does not guarantee that search will find a worthwhile opportunity, that the subject can change, or that any later recommendation, choice, programme, Work, or effect will succeed.

DOCA.1:10 - Rationale

The earliest reusable contribution is not generic goal setting or decision-support engagement. Opportunity construction often begins before a decision, option set, or separate adviser exists. Yet a fully unbounded discovery activity cannot distinguish useful exploration from fashion following.

The selected boundary is therefore intentionally small: enough identity, use, horizon, protection, posture, and effort to choose one missing result. Characterization, opportunity search, problem construction, support configuration, reachability, portfolio retention, advising, and refresh remain separable because each changes the practitioner’s action and can be entered or stopped independently.

DOCA.1:11 - SoTA-Echoing

Practice question. How should early opportunity or idea work begin before a solution-development commitment while remaining usable across unlike development subjects?

Best-known line for this pattern. ISO 56007:2023 supplies the current opportunity/idea-management boundary before solution development and deployment. FPF E.10.DEV supplies the stronger cross-holder repair: identify the changed or represented subject, claim posture, direction basis, and direct owner rather than treating development as one mechanism. This pattern adapts those contributions in DOCA.1:4.1–4.7 by adding the receiving use, protected conditions, proportional inquiry budget, independent no-adviser entry, first-missing-result return, and explicit stop.

Serious alternative or default. A project brief that starts with a fixed goal and preferred solution is cheaper when the problem and option boundary are already adequate. Unbounded ideation is more open when the inquiry is exploratory. The first excludes useful pre-goal discovery; the second lacks a proportional return. At comparable initial effort, the bounded inquiry preserves both openness and an inspectable next result, at the price of leaving more conclusions provisional.

Source roles and limits. ISO 56007 is a normative opportunity/idea-management source, not evidence of effectiveness or a universal cross-holder procedure. E.10.DEV is the internal best-known line for semantic recovery, not a holder-specific development Method. Domain, professional, legal, safety, evidence, and decision practices retain their conclusions.

Reopen condition. Reopen this source stance if a current alternative demonstrates a lower-effort entry that preserves subject and posture distinctions, receiving use, protections, independent branch entry, proportional stopping, and exact owner return, or if ISO 56007 changes the opportunity-to-solution boundary relied on here.

DOCA.1:12 - Relations

• Uses: E.10.DEV to recover the subject, posture, and direct owner when development wording changes the next action.
• Prepares: DOCA.1.CHR when selected characteristics and current, intended, protected, or unknown readings are the first missing result.
• Prepares: DOCA.2 or DOCA.3 when the inquiry needs materially different leads or a worthwhile problem and proposed contribution.
• Coordinates with: DOCA.7 when a distinct recommending performer and recipient make advising admissibility current; this pattern does not establish that relationship.
• Returns to: the exact holder, evidence, professional, legal, safety, engineering, organization, operations, strategy, research, or other practice that owns a missing premise.
• Hands later comparison and recommendation outward: current Problem Structuring and Decision Support patterns own formed decision alternatives, comparison, recommendation, follow-up, and choice separation.
• Does not imply: a Method sequence, programme, WorkPlan, performed Work, authorization, beneficial effect, publication order, or product membership.

DOCA.1:End

DOCA.1.CHR - Characterize the Development Subject and Intended Change

Type: DPF pattern

Status: Released; evolving

Normativity: Normative unless marked informative.

DOCA.1.CHR:0 - Use This When

Which characteristics would actually change this development inquiry?

Use this pattern when a person, organization, community arrangement, AI configuration, engineered system, facility, research programme, episteme, or another subject is described by a maturity label, Method list, role name, benchmark, dashboard, or one score, but the opportunity depends on more specific current, intended, protected, or unknown characteristics. The first useful result is a bounded development-facing characterization with the unknown or limitation that matters to this inquiry. A measurement, comparison, or source request is a continuation only when its obtainable contribution warrants the whole burden.

Use it after DOCA.1 when the subject, receiving use, and horizon were still loose, or enter directly when those are already clear. It can serve either opportunity construction or bounded advising. It does not diagnose every property of the subject, choose a direction, prove capability, authorize intervention, or establish that development occurred.

Cheap exit. Reuse an existing characterization when it covers the same subject and configuration, receiving use, horizon, characteristic meanings and scales, evidence window, protected conditions, and current question. If one domain practice already supplies the complete adequate characterization, use that result directly and retain its qualification.

Ordinary non-use boundary. Do not build a characterization merely because a dashboard exists. If no characteristic could change the next action, stop. Characterizations of populations, lineages, cultures, organizations, people, AI models, and engineered systems rely on different domain owners and evidence; similar metric labels do not justify transfer.

DOCA.1.CHR:1 - Problem Frame

Development talk often compresses a subject into “junior,” “mature,” “ready,” “high potential,” “advanced,” “safe,” or a composite score. A list of methods or technologies can create the same illusion: possession or use is treated as a characteristic of the subject and then as proof of useful change.

A development opportunity needs a more selective account. The practitioner must know which characteristics can reverse the worthwhile problem, proposed contribution, supported direction, reachability claim, portfolio position, advice, or protected condition. The account must preserve distinct result, resource, affected-System or distributional, and explicitly protected coordinates rather than hiding them inside a single attractive number.

This pattern governs that inquiry-relative characterization. Measurement, diagnosis, capability, architecture, safety, financial, legal, professional, organizational, engineering, research, and other domain claims retain their direct owners.

DOCA.1.CHR:2 - Problem

Without a development-facing characterization:

• a maturity word hides several unlike scales and value directions;
• a score is reused without its subject, characteristic, scale, method, uncertainty, or time stance;
• the intended condition is described without a current baseline;
• one desired gain suppresses resource use, affected-System consequences, distributional effects, or protected conditions;
• person evidence is transferred to an organization or AI configuration;
• architecture characteristics are applied when architecture is not the bearer;
• an unknown premise is silently converted to a favorable reading; and
• a later change cannot be traced to the smallest affected opportunity claim.

The resulting direction may sound specific while remaining unmeasurable, incomparable, or unsafe to rely on.

DOCA.1.CHR:3 - Forces

DOCA.1.CHR:4 - Solution

Build the smallest characteristic account that can change this inquiry, and expose every material unknown or protected coordinate.

DOCA.1.CHR:4.1 - Bind the characterization to one subject, use, and horizon

Name the exact subject and configuration. For an AI case, distinguish model, data, scaffold, tools, oversight, access, and surrounding operating arrangement when their differences matter. For an organization, name the organization or bounded arrangement rather than treating its chart or provider as the subject. For a person, name the person and relevant later-Work context.

State the receiving use, horizon, scenarios, and evidence window. A characterization for today’s incident-review Work is not automatically valid for a future management role. A model benchmark in one configuration does not characterize another configuration with the same product label.

If those boundaries are missing, use DOCA.1 and return only after they are adequate for the current question.

DOCA.1.CHR:4.2 - Select characteristics by decision difference

For each candidate characteristic, ask: if its current reading, intended reading, polarity, or uncertainty were different, could the worthwhile problem, contribution, direction, reachability, protection, advice, or next question change?

Keep it when the answer is yes. Otherwise omit it from the working account, while naming any intentionally unsearched area whose omission could reverse the result.

Start from several directions when useful:

• the receiver’s required result or acceptance expectation;
• resources and burdens needed to obtain it;
• consequences for affected Systems or groups;
• conditions that must not worsen;
• the subject’s current limitations or enabling strengths;
• prerequisites, complements, constraints, interactions, and transition conditions; and
• uncertainty or information whose resolution could change the next action.

A generic capability, maturity, readiness, quality, or performance catalogue is a source of questions, not an automatic closed set.

DOCA.1.CHR:4.3 - Define each selected characteristic and reading

For every selected characteristic, state in ordinary language:

1. what exact subject or relation bears it;
2. what the characteristic means for this receiving use;
3. its scale or admissible levels and any unit;
4. polarity—higher-is-better, lower-is-better, target-is-best, or no simple order;
5. time stance and evidence window;
6. current reading and uncertainty, or unknown;
7. intended, threshold, exploratory, or comparison reading;
8. explicitly protected reading or boundary when current;
9. source, method, and qualification needed for reliance; and
10. the next claim that this reading can change.

Use C.16 when a value, score, sensor indication, rating, or comparison must be made interpretable as a measurement. A label, dashboard tile, method description, or evidence link is not the measurement result or the actual subject state.

DOCA.1.CHR:4.4 - Orient the complete comparison coordinate set

When a finite candidate change is current, use C.11.CRC to compare an actual or relied-on configuration S0, finite change Δ, and realizable candidate configuration S1 under the same boundary, horizon, scenarios, constraints, interactions, transition basis, evidence window, and receiving decision.

Keep four coordinate families visible:

• result coordinates: what useful results may improve, worsen, or remain unchanged;
• resource coordinates: time, attention, capital, computation, energy, materials and other consumed means;
• affected-System and distributional coordinates: consequences for other Systems, groups, services, or environments and how gains and burdens are distributed; and
• explicitly protected coordinates: values that may not be silently exchanged for a gain elsewhere.

State required authority separately as a condition for proceeding. Include the time, fees or other resources needed to obtain or maintain permission when they matter, without treating permission itself as a consumed quantity.

Do not hide one family inside another or average incomparable scales. A Pareto-improvement claim is warranted only when the declared complete set has no worsening coordinate and at least one improving coordinate under the same basis. Otherwise use only supported language such as beneficial, harmful, dominated, non-dominated, or indeterminate. None of these selects the direction.

DOCA.1.CHR:4.5 - Return characteristic meaning and evidence to direct owners

Use the practice that owns the substantive characteristic:

• human capability and representative later-Work evidence remain with current HCD and capability patterns;
• organization contribution, positions, assignments, arrangements, culture, and change remain with current organization and strategy practices;
• AI/model evaluation, data, safety, security, oversight, and deployment claims remain with their direct engineering and governance owners;
• service, flow, reliability, safety, and operability remain with operations, engineering, safety, and domain practices as applicable;
• architecture characteristics use C.32.ACS or C.32.ACE only when architecture is the bearer;
• measurement meaning and work use C.16; and
• evidence reliance, provenance, and currentness use their direct FPF owners.

Record an available MethodDescription as a way a result might be obtained, not as the result. Mark a source-qualified unknown when measurement, access, or currentness is insufficient.

When a reading was established for a different bearer or configuration, rely on it only when the direct practice that owns the receiving characteristic supplies a qualified transfer basis covering the receiving bearer and configuration, characteristic meaning, scale, intended use, evidence window, and uncertainty. Without that basis, keep the receiving reading unknown and limit the affected opportunity claim. This can finish a useful characterization. Use A.15.9 and C.11.DUA to select an evidence request only when its obtainable contribution warrants formulation, qualification, supplier Work, delivery, interpretation, delay, and displaced work.

DOCA.1.CHR:4.6 - Write the bounded characterization

Use ordinary prose first. This compact form can carry a characterization across a multi-practice handoff:

DevelopmentFacingCharacterization@Context:
  subjectAndConfiguration:
  receivingUse:
  horizonScenariosAndEvidenceWindow:
  selectedCharacteristics:
    - characteristicAndBearer:
      meaningForThisUse:
      scaleUnitPolarityAndTimeStance:
      currentReadingAndUncertainty:
      intendedOrExploratoryReading:
      protectedReadingOrBoundary:
      directOwnerAndSource:
      affectedOpportunityClaim:
  completeCoordinateSet:
    resultCoordinates:
    resourceCoordinates:
    affectedSystemOrDistributionalCoordinates:
    explicitlyProtectedCoordinates:
  materialUnknowns:
  selectedFurtherContributionIfNeeded:
  stopOrReopenCondition:

Include only fields that serve the receiving use; an inactive request needs no field or explanation. This local form is not a universal characteristic space, measurement result, diagnosis, criterion verdict, capability profile, decision, or authorization. Several selected characteristics may use different scales and result epistemes.

DOCA.1.CHR:4.7 - Choose the next truthful result

Return one of these outcomes:

• an adequate characterization ready for opportunity search or construction;
• a worthwhile obtainable measurement or evidence request tied to one affected claim;
• a comparison question with the complete coordinate set;
• a narrower characterization that supports only part of the opportunity;
• a blocker because a protected or decision-reversing reading is unavailable;
• an explicit unknown that limits the answer while the supported characterization remains useful; or
• a stop because the existing characterization already serves the receiving use.

Continue to DOCA.2 when material opportunity-generating dimensions are now visible, to DOCA.4 when a direction needs a finite characteristic change and support configuration, to DOCA.5 when joint reachability is current, or to DOCA.7 when a formed advice question needs an admissible relationship. These are conditional continuations, not a fixed order.

DOCA.1.CHR:4.8 - Reopen the smallest affected scope

Reopen when the subject or configuration, receiving use, horizon, scenario, characteristic meaning, scale, polarity, measurement method, evidence window, protected condition, or decision-relevant unknown changes. Trace that change to the smallest affected opportunity, comparison, or advice claim.

Do not discard unaffected readings merely because one characteristic changed. Do not retain a composite maturity score when its underlying meaning or weighting changed.

DOCA.1.CHR:4.9 - What changes in practice

The practitioner replaces “more mature,” “AI-ready,” “senior,” or “platform-capable” with the characteristics that alter this inquiry. Current, intended, protected, and unknown readings stay distinct. Missing evidence limits the affected reading; a worthwhile further contribution becomes a directed request. Later comparison retains benefits, burdens, affected Systems, distribution, and protections on their own scales.

DOCA.1.CHR:5 - Archetypal Grounding

DOCA.1.CHR:5.1 - Person and representative later Work

Mira’s bounded inquiry concerns incident-review and handoff Work over four months. “Become better at AI” is discarded as a characteristic. The selected characteristics are: time to identify a material handoff gap, quality of the explanation supplied to the next reviewer, ability to detect unsupported model output, confidential-data exposure, review workload, and transfer to two representative incident classes.

The current account has qualified examples for explanation quality and workload, but no comparable evidence for transfer or unsupported-output detection. Those readings remain unknown. The intended contribution is faster detection without worsening explanation quality, confidentiality, or sustainable workload. HCD owns the human demand, capability, support, and transfer evidence. The characterization returns those useful readings and unknowns; it supplies no course recommendation or transfer claim. Representative-Work evidence becomes a request only when the attainable contribution warrants acquisition for the next use.

DOCA.1.CHR:5.2 - Organization without one maturity score

An engineering organization is called “low maturity” because releases are slow. The inquiry concerns reliable product-family delivery over twelve months. The characterization separates release lead time, rework, service interruption, platform reuse, security exposure, scarce-specialist attention, team autonomy, and customer-impact distribution.

Lead time has a lower-is-better quantity scale under a stated window; team autonomy has an ordinal scale and no ratio arithmetic; security exposure uses separately governed risk results. The intended configuration may improve lead time while worsening specialist bottlenecks or security. The account therefore remains multi-coordinate and indeterminate until organization, platform, operations, and security owners provide the missing premises.

DOCA.1.CHR:5.3 - AI arrangement and configuration identity

A team wants to “improve the model.” The actual subject is a model edition with a retrieval corpus, tool permissions, evaluator, human escalation path, and operating environment. Selected characteristics include task success under the declared evaluation, false-action rate, explanation adequacy, data exposure, escalation latency, compute use, operator workload, and robustness to changed inputs.

A benchmark from the bare model does not characterize the deployed arrangement. Human learning evidence does not establish model adaptation. The next question is whether the current evaluation covers the intended tool-enabled configuration and protected safety/security conditions.

DOCA.1.CHR:5.4 - Already adequate characterization

A facility team already has current, source-qualified service, safety, operability, resource, and affected-community characteristics for the same configuration and horizon. No meaning, scale, or evidence window changed. The team reuses the account and proceeds to joint reachability. Reformatting it into this pattern’s compact form would add burden without changing action.

DOCA.1.CHR:6 - Bias-Annotation

• Score realism: a number can feel more objective than its method, scale, weighting, and uncertainty warrant.
• Maturity ladder bias: one ordered label invites a universal sequence and higher-is-better assumption.
• Human transfer bias: person learning and capability measures do not characterize organizations, AI arrangements, or engineered systems.
• Architecture projection: architecture characteristics are tempting general quality labels; use them only when architecture is the bearer.
• Available-data bias: easily measured coordinates can crowd out protected or distributional consequences that matter more.
• Benefit-only selection: desired result coordinates can hide resources, affected Systems, transition burdens, and option losses.
• Unknown-to-zero bias: missing evidence is neither absence nor a favorable baseline.
• Form completion bias: a full table does not supply qualified measurements or direct-owner conclusions.

DOCA.1.CHR:7 - Conformance Checklist

A conforming characterization or companion account:

1. MUST identify the subject and configuration, receiving use, horizon, scenarios, and evidence window.
2. MUST select each characteristic by an explicit way it can change the current inquiry or a protected condition.
3. MUST state the bearer, meaning, Scale or levels, Unit when applicable, polarity, and time stance for every relied-on characteristic.
4. MUST distinguish current, intended or exploratory, protected, and unknown readings.
5. MUST keep result, resource, affected-System or distributional, and explicitly protected coordinate families visible when finite comparison is current.
6. MUST NOT force incomparable coordinates into one scalar or assert Pareto improvement without a complete oriented set under one basis.
7. MUST identify the direct owner, source, qualification, and uncertainty for every decision-reversing reading.
8. MUST NOT use a MethodDescription, dashboard, benchmark, source link, or tool output as proof that measurement Work or a result exists.
9. MUST return each missing premise as a bounded request, unknown, narrower claim, blocker, or stop.
10. MUST retain a next measurement, comparison, pattern, direct-owner use, or local reopen condition only where it changes the recipient’s continuation or interpretation. A sufficient direct characterization creates no further-work or omission-record obligation.
11. MUST NOT present the characterization as a chosen direction, recommendation, programme, authorization, performed Work, or observed effect.
12. SHOULD make the first useful result readable without requiring the compact form.

DOCA.1.CHR:8 - Common Anti-Patterns and How to Avoid Them

DOCA.1.CHR:9 - Consequences

Practitioners gain a characterization that is smaller than a full diagnosis yet strong enough to guide opportunity construction, source requests, finite comparison, or advice. Several scales and unknowns can coexist without pretending to be one score. Protected conditions become visible before selection, and later premise changes can reopen only the claims that depended on them.

The cost is that a familiar word such as maturity may unfold into several claims with different owners and evidence windows. Some apparently precise numbers become conditional or unusable. Completing the account may require measurements or specialist results that the current inquiry cannot afford.

This pattern improves the integrity of the inquiry, not the subject itself. It supplies no measurement Work, capability, diagnosis, direction choice, intervention, assurance, or observed effect.

DOCA.1.CHR:10 - Rationale

The common contribution is not one cross-holder scale. It is the action of selecting and orienting characteristics for one subject, receiving use, horizon, and opportunity question, then returning their substantive meanings and evidence to direct owners.

In opportunity construction, use the characterization to vary opportunity-generating dimensions and specify finite candidate changes. In advising, use it to recover premises that can reverse a comparison or recommendation.

DOCA.1.CHR:11 - SoTA-Echoing

Practice question. How should practitioners replace a development maturity label or isolated score with a characterization that can guide a finite opportunity decision without inventing one universal scale?

Best-known line for this pattern. FPF C.16 supplies the strongest current measurement chain: exact measurand or subject, Characteristic, Scale, method, model, calibration, dated Work, attributed result, uncertainty, and bounded later use. C.11.CRC supplies the strongest current finite-change orientation: actual S0, finite Δ, realizable S1, complete result/resource/affected-System/distributional/protected coordinates, interactions, transition basis, uncertainty, and option effects. This pattern adapts those lines at DOCA.1.CHR:4.2–4.7 by selecting only characteristics that can change one development inquiry and by returning holder-specific meaning and evidence outward.

Serious alternative or default. A maturity model or composite readiness score is faster to communicate and may be adequate when its construct, scale, weighting, evidence, and decision use are already qualified. As a default across unlike holders, it hides scale legality, trade-offs, protected coordinates, and transfer. At comparable entry effort, the selected multi-coordinate characterization preserves more decision-relevant information, at the cost of a less compact headline and possible indeterminate result.

For organization and campaign cases, ISO 56008:2024 is a current opportunity/innovation measurement source and supports explicit measurement and portfolio review. It is an organization-scope comparator, not a universal person, AI, or engineered-system characterization Method and not effectiveness evidence.

Source roles and limits. C.16 and C.11.CRC are the current best-known FPF lines for measurement and finite contribution comparison. ISO 56008 is a bounded normative comparator. Holder, domain, safety, professional, legal, and evidence practices supply the actual characteristic meanings and results; this pattern does not outrank them.

Reopen condition. Reopen this stance if a current alternative demonstrates a lower-burden characterization that preserves subject/configuration identity, scale and uncertainty, the complete coordinate set, protected conditions, holder-specific ownership, and local reopenability, or if a relied-on measurement or finite-comparison pattern changes those obligations.

DOCA.1.CHR:12 - Relations

• Receives from: DOCA.1 the subject, receiving use, horizon, protected conditions, posture, and effort boundary when those were not already adequate.
• Uses: C.16 for relied-on measurement claims and C.11.CRC for finite configuration-relative contribution comparison.
• Prepares: DOCA.2 by exposing opportunity-generating characteristics and relevant unsearched dimensions.
• Constrains: DOCA.3 and DOCA.4 by making the receiving problem, contribution, finite change, and protections inspectable.
• Supplies premises to: DOCA.5, DOCA.6, DOCA.7, and DOCA.8 without establishing reachability, portfolio admission, advising admissibility, or refresh outcome.
• Returns to: HCD or capability owners for human results; organization, strategy, engineering, operations, AI/model, safety, legal, professional, research, evidence, measurement, or other direct owners for their characteristics and conclusions.
• Does not imply: one maturity scale, beneficial development, a chosen direction, recommendation, programme, WorkPlan, performed Work, assurance, or effect.

DOCA.1.CHR:End