Library / Development Opportunity Construction and Development-Direction Advising Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:40:05 UTC

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.”