World Models · public research draft

Plan / Schedule

Represent intentions bound to time: what an agent intends to do, how firmly, when, in what order, under which commitments, and how the intention was later revised or realized.

AI YAMLAGENTS.mdResearch evidence
Research draft. The Claude + Grok synthesis is public for review and use with caution. It passed structural validation but is not yet a canonical Vercy release because the source and coverage holds below remain open.
Catalogue IDWM-ACT-008
Version0.3.0-research.1
Previous version-
Typeaggregate
ValidationPassed
Synthesis digestsha256:41f21cb666ec94fe…
23Sources
6Bundles
13Layers
32Findings
130Questions
31Artifacts
Format-independent logical structure

Bundles → Layers → Findings → Questions + Artifacts

b-plan-identity-and-authorityPlan Identity and Authority2 layers

What one plan is, how firmly it is intended, how its revisions are ordered, and who may change it.

l-identity-and-classificationIdentity and Classification2 findings

The stable handle for a plan, its boundary against neighbours, and the class and strength of intention it asserts.

f-plan-identity-and-boundary

Plan identity and boundary

Establishes the immutable handle for one plan instance and what falls inside its envelope rather than in a referenced plan, task or project.

Questions
  1. Which identifier is the authoritative, immutable handle for this plan, and which system issued it?identity
    Expected answer
    • Master-system identifier value
    • Issuing system reference
    • Identifier scheme or namespace
    • Locally-minted flag
  2. What distinguishes this plan from the adjacent plans, tasks and projects it references?definition
    Expected answer
    • Boundary statement
    • Excluded neighbour references
    • Rationale for separate identity
  3. What planning horizon and time granularity does the plan claim to cover?temporal
    Expected answer
    • Horizon start and end
    • Granularity unit
    • Coverage caveat
  4. Which planned actions and schedule entries are constituent parts rather than merely referenced?composition
    Expected answer
    • Member references with part or reference role
    • Containment rule
Artifacts
  • Plan recordThe canonical object carrying plan identity, boundary, membership and horizon, from which all projections are derived.
f-plan-type-and-intent-mode

Plan type and intent mode

Classifies the kind of plan and the degree of authority its intention carries, which governs what an agent may act on unaided.

Questions
  1. What degree of authority does this plan assert: proposal, plan, directive or order?classification
    Expected answer
    • Intent mode code
    • Value set reference
    • Authorizing statement
  2. Which plan kind applies, such as project schedule, operational routine, agent action plan or service plan?definition
    Expected answer
    • Plan kind code
    • Domain profile reference
  3. Which parties may act on this plan without a further approval step?authority
    Expected answer
    • Authorized actor references
    • Approval-required flag
    • Escalation path
  4. On what scale is priority or urgency expressed, and what does each level oblige?measurement
    Expected answer
    • Priority value
    • Scale definition and direction
    • Obligation per level
Artifacts
  • Intent mode value setPublished controlled vocabulary of intent modes and plan kinds, with the obligation attached to each level.
l-versioning-ownership-and-authorityVersioning, Ownership and Authority2 findings

How revisions are ordered and reconciled, who owns the plan, and what authorization made it current.

f-plan-version-and-supersession

Plan version and supersession

How successive revisions of one plan are counted, timestamped, reconciled between replicas and retired.

Questions
  1. Which changes require the revision counter to increment, and which do not?constraint
    Expected answer
    • Material field list
    • Counter increment rule
    • Exempt field list
  2. When two replicas hold the same plan identifier, which revision wins and by what tiebreak?interoperability
    Expected answer
    • Precedence order: identifier, counter, modification timestamp
    • Escalation rule for exact ties
  3. How is a superseded revision marked, and does it remain retrievable?lifecycle
    Expected answer
    • Revision state code
    • Supersedes and superseded-by references
    • Retrievability policy
  4. Which timestamp records the modification event as opposed to receipt of that modification?temporal
    Expected answer
    • Modification timestamp
    • Ingestion timestamp
    • Clock source
Artifacts
  • Plan revision historyAppend-only ordered record of plan revisions with counters, timestamps and supersession links.
f-ownership-authority-and-approval

Ownership, write authority and approval

Who is accountable for the plan, who holds write authority over the master copy, and what evidences approval.

Questions
  1. Which agent is accountable for this plan and its schedule entries?ownership
    Expected answer
    • Owner agent reference
    • Accountability statement
    • Effective from timestamp
  2. Which single role holds write authority over the master copy, and how is that authority transferred?authority
    Expected answer
    • Organizer or scheduler reference
    • Transfer procedure
    • Transfer record
  3. What evidence records that the plan was approved, by whom and against which revision?evidence
    Expected answer
    • Approver reference
    • Approval timestamp
    • Approved revision counter
    • Approval artifact reference
  4. Under what conditions may write or approval authority be delegated, and is the delegation recorded on the plan?access
    Expected answer
    • Delegation grant
    • Scope and expiry
    • Delegator and delegate references
Artifacts
  • Plan approval recordSigned or attributed record binding an approver to a specific plan revision, used as evidence for authority claims.
b-intention-contentIntention Content2 layers

What is intended: goals, planned actions, and the conditions and uncertainties the intention rests on.

l-goals-and-planned-actionsGoals and Planned Actions2 findings

The intended end state and the individual actions meant to bring it about.

f-goal-and-success-criteria

Goal and success criteria

The end state the plan serves and the measurable test by which fulfilment is judged.

Questions
  1. What end state or objective does the plan intend to bring about?definition
    Expected answer
    • Goal statement
    • Scope of effect
    • Beneficiary of the outcome
  2. By which measurable criterion is the goal judged achieved rather than merely attempted?measurement
    Expected answer
    • Criterion expression
    • Measurement unit and threshold
    • Evaluation point
  3. How does the goal decompose into sub-goals and planned actions?composition
    Expected answer
    • Parent goal reference
    • Child goal references
    • Decomposition rule
  4. What happens when two goals in the same plan cannot both be satisfied?exception
    Expected answer
    • Precedence rank
    • Tradeoff rule
    • Escalation owner
Artifacts
  • Goal specificationStatement of objectives, decomposition and success criteria against which the plan's fulfilment is assessed.
f-planned-action-specification

Planned action specification

One intended action: its type and object, the conditions required to start it, the effects expected, and whether it is instantaneous or durative.

Questions
  1. Which action type and target object does the planned action denote?definition
    Expected answer
    • Action type code
    • Target object reference
    • Parameter bindings
  2. Which conditions must hold for the planned action to be executable?requirement
    Expected answer
    • Precondition expression
    • Condition timing: at start or over all
    • Checking responsibility
  3. Which state changes does the planned action expect to produce?state
    Expected answer
    • Expected effect expression
    • Effect timing: at start or at end
    • Affected entity references
  4. Is the action instantaneous or durative, and are its conditions checked at start, throughout, or at end?temporal
    Expected answer
    • Durativity flag
    • Condition annotation per clause
    • Duration constraint
  5. Which lifecycle states may a planned action occupy before it is realized?lifecycle
    Expected answer
    • State code list
    • Allowed transitions
    • Terminal pre-realization states
Artifacts
  • Planned action definitionDefinition of one intended action with parameters, preconditions, expected effects and durativity.
l-assumptions-and-uncertaintyAssumptions and Uncertainty2 findings

Conditions the plan relies on but does not control, and the modelled uncertainty in its durations and logic.

f-assumption-and-precondition-register

Assumption register

External conditions the plan takes for granted, who watches them, and what their failure invalidates.

Questions
  1. Which external condition does the plan take for granted without controlling it?definition
    Expected answer
    • Assumption statement
    • Controlling party if any
    • Basis for believing it
  2. Who is accountable for monitoring each assumption, and on what cadence?ownership
    Expected answer
    • Monitoring agent reference
    • Review cadence
    • Last reviewed timestamp
  3. Which observable signal invalidates the assumption, and what re-planning does it trigger?event
    Expected answer
    • Signal definition
    • Threshold
    • Triggered response
  4. How much of the plan fails if this assumption fails?measurement
    Expected answer
    • Sensitivity rating
    • Dependent item references
    • Estimated impact
Artifacts
  • Assumption registerMaintained list of assumptions with owners, monitoring signals, sensitivity and current state.
f-schedule-risk-and-contingency

Schedule risk and contingency

Uncertainty in durations and logic, the analysis run against it, and the reserve held to absorb it.

Questions
  1. Which duration estimates carry a distribution rather than a single deterministic value?measurement
    Expected answer
    • Optimistic, most likely and pessimistic values
    • Distribution type
    • Basis of estimate
  2. Has a schedule risk analysis been run, against which plan revision, and at what confidence level is the committed date set?validation
    Expected answer
    • Analysis run reference
    • Analysed revision counter
    • Confidence percentile
    • Resulting date
  3. Where is schedule reserve held, and who may authorize consuming it?constraint
    Expected answer
    • Reserve location in the network
    • Reserve duration
    • Consumption authority
  4. Which activities drive the greatest schedule risk?relationship
    Expected answer
    • Ranked driver activity references
    • Sensitivity measure
    • Correlation assumptions
Artifacts
  • Schedule risk analysis reportRecord of a risk analysis run: inputs, distributions, resulting confidence curve, driver ranking and the revision analysed.
b-temporal-bindingTemporal Binding2 layers

Binding intentions to instants, intervals, deadlines, durations and repeating patterns, with correct time zone semantics.

l-time-anchors-zones-and-durationTime Anchors, Zones and Duration3 findings

How an entry is anchored on a timeline, in which time form, and what its duration means.

f-schedule-entry-time-binding

Schedule entry time binding

The anchoring of a planned action to a point, an interval, a deadline, or a start plus duration.

Questions
  1. Is the entry anchored as an instant, a start plus duration, a start plus end, or a deadline only?temporal
    Expected answer
    • Anchor form code
    • Start value
    • End or duration or due value
  2. In which serialization profile and precision are the entry's absolute times expressed?constraint
    Expected answer
    • Timestamp profile reference
    • Seconds precision
    • Offset or Z designator
    • Leap-second handling
  3. Is the entry a date-only all-day binding or a time-of-day binding?classification
    Expected answer
    • Date-only flag
    • Local day boundary rule
  4. Where is the entry expected to take place, and does that place determine its local time?spatial
    Expected answer
    • Location reference or text
    • Coordinates if known
    • Whether location drives the time zone
Artifacts
  • Schedule entryThe time binding of a planned action, carrying anchor form, times, place and its relation to the intention it times.
f-time-zone-and-floating-time

Time zone and floating-time integrity

Which of the three time forms an entry uses, and how future local times survive time zone rule changes.

Questions
  1. Is the entry stored as UTC, as local time with a named zone, or as floating local time?classification
    Expected answer
    • Time form code
    • Zone identifier when applicable
    • Justification for floating form
  2. Which time zone database release was in force when the entry was created, and is that release recorded?provenance
    Expected answer
    • Database release identifier
    • Recording policy
    • Recomputation trigger
  3. What happens to a future entry when its zone's offset or daylight-saving rule changes?exception
    Expected answer
    • Recomputation rule
    • Notification obligation
    • Affected entry list
  4. If a stored offset disagrees with the named zone, which one governs?validation
    Expected answer
    • Precedence rule
    • Criticality marking of the zone tag
    • Error handling behaviour
Artifacts
  • Time zone binding policyThe owner package's declared rules on which time form to use per entry class, whether zone tags are critical, and how zone data releases trigger recomputation.
f-duration-effort-and-working-calendar

Duration, effort and working calendar

Whether a stated duration means elapsed time, working time or resource effort, and which calendar converts between them.

Questions
  1. Does the stated duration mean elapsed time, working time, or resource effort?definition
    Expected answer
    • Duration kind code
    • Conversion rule
    • Declared default
  2. Which working calendar, including non-working days and shift hours, applies to this entry?composition
    Expected answer
    • Calendar reference
    • Working day pattern
    • Holiday set and locale
  3. In which units are durations expressed, and how are partial units rounded?measurement
    Expected answer
    • Unit code
    • Rounding rule
    • Minimum granularity
  4. Which calendar governs when the resource calendar and the activity calendar disagree?exception
    Expected answer
    • Precedence rule
    • Override record
    • Responsible role
Artifacts
  • Working calendar definitionNamed calendar of working days, shift hours, holidays and exceptions used to convert between elapsed, working and effort durations.
l-recurrence-and-exceptionsRecurrence and Exceptions2 findings

Generative patterns for repeating intentions and the individual occurrences that deviate from them.

f-recurrence-rule-specification

Recurrence rule specification

The pattern that generates repeated occurrences, its grammar, anchor and termination.

Questions
  1. In which recurrence grammar is the pattern expressed, and is it losslessly convertible to the others in use?interoperability
    Expected answer
    • Grammar identifier
    • Convertibility matrix
    • Known lossy constructs
  2. Which frequency, interval, by-part and termination terms define the pattern?constraint
    Expected answer
    • Frequency code
    • Interval value
    • By-part values
    • Until or count
  3. Which start value anchors expansion, and in which zone is expansion performed?temporal
    Expected answer
    • Anchor start value
    • Expansion zone
    • Week start setting
  4. Is the series bounded by count, by an end date, or unbounded, and how far should a consumer expand it?process
    Expected answer
    • Boundedness code
    • Horizon policy
    • Maximum occurrences returned
Artifacts
  • Recurrence ruleThe stored generative pattern; the rule plus its overrides, not the expanded occurrence list, is the canonical form.
f-occurrence-override-and-exception

Occurrence override and exception

Individual occurrences that differ from the series or are removed from it, and how they survive rule changes.

Questions
  1. How is a single occurrence identified independently of the series it belongs to?identity
    Expected answer
    • Series identifier
    • Recurrence identifier value
    • Identifier stability rule
  2. Does a change apply to one occurrence only or to that occurrence and all later ones?composition
    Expected answer
    • Range flag
    • Affected occurrence set
    • Resulting split series
  3. How are cancelled or excluded occurrences recorded so that expansion does not regenerate them?exception
    Expected answer
    • Exclusion date list
    • Cancellation status per occurrence
    • Tombstone retention period
  4. When the series rule changes, what becomes of previously detached overrides?validation
    Expected answer
    • Reconciliation rule
    • Orphaned override handling
    • Operator notification
Artifacts
  • Occurrence override setThe collection of per-occurrence patches, additions and exclusions that qualify a recurrence rule.
b-network-feasibility-and-integrityNetwork, Feasibility and Integrity2 layers

Ordering between intended items, imposed date constraints, the dates derived from them, resource feasibility and whether the result is fit to rely on.

l-dependency-and-constraint-networkDependency and Constraint Network4 findings

Logical ordering between planned items, externally imposed date constraints, and the checks that decide whether the network is sound.

f-ordering-dependency-and-lag

Ordering dependency and lag

The directed relations that sequence planned items, their type, lag and justification.

Questions
  1. Which ordering relation holds between predecessor and successor: finish-to-start, start-to-start, finish-to-finish or start-to-finish?relationship
    Expected answer
    • Dependency type code
    • Predecessor reference
    • Successor reference
  2. What lag or lead applies, in which duration kind, and what justifies it?measurement
    Expected answer
    • Lag value and sign
    • Duration kind
    • Calendar used to apply the lag
  3. What physical or contractual reason justifies the dependency rather than mere convenience?evidence
    Expected answer
    • Rationale statement
    • Evidence reference
    • Reviewer and review date
  4. Which dependencies cross the plan boundary to another party's plan?interoperability
    Expected answer
    • External plan reference
    • Counterparty agent
    • Agreed handover point
    • Notification obligation
Artifacts
  • Dependency networkThe directed acyclic set of ordering relations with types, lags and rationale, from which schedule dates are computed.
f-date-constraint-and-flexibility

Date constraint and scheduling flexibility

Externally imposed date constraints on an entry and how far the entry may move without breaching them.

Questions
  1. Which date constraint is imposed on this entry, and who imposed it?constraint
    Expected answer
    • Constraint type code
    • Constraint date value
    • Imposing party reference
  2. How flexible is the entry: fixed, movable within a window, or freely schedulable?classification
    Expected answer
    • Flexibility class
    • Permitted movement window
    • Approval needed to move
  3. When a hard constraint conflicts with network logic, which is honoured and how is the conflict surfaced?exception
    Expected answer
    • Precedence rule
    • Conflict marker
    • Notification target
  4. Is the deadline self-imposed, contractual or regulatory?authority
    Expected answer
    • Deadline basis code
    • Governing instrument reference
    • Consequence of breach
f-schedule-integrity-and-quality

Schedule integrity and quality assessment

Structural checks that decide whether a schedule is complete, well-constructed and credible enough to be relied on.

Questions
  1. Does the schedule capture every activity needed to meet the objective, including work performed by other parties?quality
    Expected answer
    • Coverage assessment
    • Omitted scope list
    • Breakdown structure reference
  2. Which activities have missing predecessors or successors, negative lag, or excessive use of hard constraints?validation
    Expected answer
    • Open-end count
    • Negative lag count
    • Constrained activity count
    • Defect list with references
  3. Can the schedule be traced horizontally across dependent activities and vertically to its summary levels?evidence
    Expected answer
    • Horizontal traceability result
    • Vertical traceability result
    • Sampled evidence references
  4. Which health metrics are computed, at what thresholds, and against which scheduling run?measurement
    Expected answer
    • Metric names and values
    • Threshold set
    • Scheduling run reference
    • Pass or fail per metric
Artifacts
  • Schedule health assessmentEvidence record of integrity and quality checks against a named plan revision, usable as a gate on baseline approval.
f-plan-hierarchy-and-relationship-integrity

Precedence network and hierarchical composition

RFC 9253 extends RELATED-TO with temporal RELTYPE values FINISHTOSTART, FINISHTOFINISH, STARTTOFINISH and STARTTOSTART, plus GAP for lag (positive) or lead (negative) duration, and FIRST, NEXT, DEPENDS-ON, PARENT, CHILD and SIBLING. P-Plan isPreceededBy is a transitive step ordering without lag types. OWL-Time intervalBefore, intervalMeets, intervalOverlaps and related Allen relations describe interval topology but are not project-management lag. FHIR CarePlan.partOf, basedOn and replaces relate plan instances. REFID groups components without adding meaning. These relation families must be stored distinctly; isPreceededBy is not equivalent to FINISHTOSTART with lag.

Questions
  1. What ordering constraint holds between these planned items, including precedence type and lead or lag gap?relationship
    Expected answer
    • predecessor_id (string)
    • successor_id (string)
    • reltype (enum)
    • gap (signed-duration)
  2. Is this plan or item part of, based on, replacing, parent of or child of another plan, and what grouping REFID if any associates peers?composition
    Expected answer
    • part_of_plan_id (string)
    • based_on_plan_id (string)
    • replaces_plan_id (string)
    • reltype (enum)
    • group_refid (string)
  3. Independently of project lag, which Allen interval relation holds between the scheduled intervals of the two items?temporal
    Expected answer
    • allen_relation (enum)
    • interval_meets (boolean)
  4. Does this relationship currently dangle because the target was deleted or cancelled, as RFC 9253 warns for FIRST, NEXT and temporal links?evidence
    Expected answer
    • target_missing (boolean)
    • target_status (enum)
Artifacts
  • Dependency recordTyped relationship between planned items, including precedence type, gap and optional grouping key.
l-computation-and-resourcesComputation and Resources2 findings

Dates derived from logic, durations and constraints, and the resources whose availability makes them feasible.

f-critical-path-and-float

Critical path and float computation

Separates asserted inputs from computed outputs and records the run that produced the dates, float and critical path.

Questions
  1. Which dates are asserted inputs and which are computed outputs of a scheduling run?provenance
    Expected answer
    • Per-field derivation flag
    • Computation run reference
    • Input revision counter
  2. Which continuous path of activities determines the finish date, and how was its validity checked?validation
    Expected answer
    • Ordered path activity references
    • Validation method
    • Anomalies found
  3. What total float and free float does each activity carry, and what threshold counts as unreasonable?measurement
    Expected answer
    • Total float value
    • Free float value
    • Threshold and unit
    • Outlier activity references
  4. What triggers recomputation, and is the previous computed result retained?process
    Expected answer
    • Trigger condition list
    • Retention policy for prior runs
    • Run cadence
Artifacts
  • Scheduling run resultImmutable output of one scheduling computation: derived dates, float, critical path and the exact inputs and settings used.
f-resource-assignment-and-contention

Resource assignment and contention

Which agents and resources are assigned at what allocation, their availability, and where they are over-committed.

Questions
  1. Which agent or resource is assigned to the planned action, in which role and at what allocation?relationship
    Expected answer
    • Assignee reference
    • Assignment role
    • Allocation units
    • Effective period
  2. What availability calendar limits the assigned resource?state
    Expected answer
    • Availability window set
    • Calendar reference
    • Exception periods
  3. Where is the same resource committed to overlapping entries, and how is that resolved?exception
    Expected answer
    • Overlap detection result
    • Resolution action
    • Deciding role
  4. Which activities carry a duration but no assigned resource, and is that deliberate?quality
    Expected answer
    • Unresourced activity references
    • Justification
    • Remediation owner
Artifacts
  • Resource assignment setThe assignments and allocations for a plan revision, with detected contention, used to test feasibility.
b-commitment-and-coordinationCommitment and Coordination2 layers

Intentions that bind an agent to another party, and the negotiation by which times and participation are agreed.

l-commitment-and-obligationCommitment and Obligation2 findings

What is promised to whom, on what basis, and what follows if it is not delivered.

f-commitment-parties-and-terms

Commitment parties and terms

The subset of intentions that bind an agent toward a named beneficiary, with terms and qualifying conditions.

Questions
  1. Which party issues the commitment and which party is its beneficiary?ownership
    Expected answer
    • Assigner reference
    • Assignee or beneficiary reference
    • Third-party arbiter if any
  2. What exactly is promised, by when, and under which qualifying conditions?requirement
    Expected answer
    • Promised action
    • Deadline or interval
    • Constraint expressions
    • Referenced planned action
  3. Is the commitment informal, contractual or regulatory, and what evidence establishes it?classification
    Expected answer
    • Basis code
    • Governing instrument reference
    • Establishing evidence
  4. Who is entitled to verify the commitment's existence and terms?access
    Expected answer
    • Verifier references
    • Disclosure scope
    • Verification interface
Artifacts
  • Commitment recordRecord binding an intention to a beneficiary, carrying parties, terms, conditions and current state.
f-remedy-consequence-and-release

Remedy, consequence and release

What follows non-fulfilment of a commitment, and how commitments are honoured, released or transferred.

Questions
  1. Which additional duty is triggered when the commitment is not fulfilled?constraint
    Expected answer
    • Consequence duty definition
    • Trigger condition
    • Duty bearer reference
  2. Which observable event constitutes non-fulfilment, and at what moment is it evaluated?event
    Expected answer
    • Breach criterion
    • Evaluation instant
    • Observing party
  3. How is a commitment released, renegotiated or transferred, and whose consent is required?lifecycle
    Expected answer
    • Release procedure
    • Consenting parties
    • Resulting state and successor commitment
  4. What evidence closes the commitment as honoured?evidence
    Expected answer
    • Evidence references
    • Accepting party
    • Acceptance timestamp
Artifacts
  • Commitment settlement recordRecord of how a commitment ended: honoured with evidence, breached with consequence applied, released or transferred with consent.
l-participation-and-negotiationParticipation and Negotiation3 findings

Who is invited, what they answered, how clashes are detected and how times are renegotiated.

f-participant-role-and-response

Participant role and response state

Roles participants hold on an entry, their current response, and how delegation is represented.

Questions
  1. In which role does each participant appear on the entry?classification
    Expected answer
    • Role code
    • Required or optional flag
    • Role source vocabulary
  2. What is each participant's current response state, and when was it last updated?state
    Expected answer
    • Participation status code
    • Status update timestamp
    • Updating agent
  3. Is a reply expected from this participant, and by when?process
    Expected answer
    • Reply expected flag
    • Reply deadline
    • Reminder policy
  4. When a participant delegates, how are delegator and delegate linked on the entry?relationship
    Expected answer
    • Delegated-to reference
    • Delegated-from reference
    • Whether the delegator remains listed
Artifacts
  • Participant rosterThe set of participants on an entry with roles, response states, reply expectations and delegation links.
f-conflict-detection-and-rescheduling

Conflict detection and rescheduling

Whether an entry consumes availability, how clashes are found, and how alternative times are proposed and recorded.

Questions
  1. Does this entry consume the participant's availability or leave them free?definition
    Expected answer
    • Transparency or free-busy status code
    • Effect on availability computation
  2. How are overlapping commitments detected across separate calendars and plans?process
    Expected answer
    • Detection scope
    • Overlap rule
    • Detected conflict set
  3. How is an alternative time proposed, accepted or declined?decision
    Expected answer
    • Proposed alternative values
    • Proposing party
    • Decision outcome and decider
  4. When an entry moves, what records the previous time and the reason?provenance
    Expected answer
    • Previous start and end
    • Reason code
    • Deciding agent
    • Decision and application timestamps
Artifacts
  • Free/busy projectionAvailability-only view over a bounded horizon, disclosing busy intervals without entry content, used for conflict detection across parties.
f-scheduling-method-and-message-sequencing

Scheduling methods and message sequencing

iTIP methods are PUBLISH, REQUEST, REPLY, ADD, CANCEL, REFRESH, COUNTER and DECLINECOUNTER. Organizer may send PUBLISH, REQUEST, ADD, CANCEL and DECLINECOUNTER; Attendee may send REPLY, REFRESH, COUNTER and a delegation REQUEST. Correlation keys are UID, RECURRENCE-ID, SEQUENCE and DTSTAMP: higher SEQUENCE obsoletes lower for the same UID and recurrence id; matching SEQUENCE ties break on later DTSTAMP. SEQUENCE MUST increment when Organizer changes DTSTART, DTEND, DURATION, DUE, RRULE, RDATE, EXDATE or STATUS. JSCalendar sequence and method (lowercase iTIP method) carry the same semantics. Out-of-order replies must be discarded using persisted last SEQUENCE and DTSTAMP per attendee.

Questions
  1. Which scheduling method is being applied, who may send it, and is this a new object or a revision of an existing UID?process
    Expected answer
    • method (enum)
    • originator_role (enum)
    • is_new_uid (boolean)
  2. What SEQUENCE and stamp time identify this revision, and does it obsolete a previously stored component with the same UID and recurrence id?lifecycle
    Expected answer
    • sequence (integer)
    • stamp_time (rfc3339-date-time)
    • obsoletes_sequence (integer)
  3. If a reply arrives with a lower sequence or earlier stamp than the last persisted attendee response, should it be discarded?evidence
    Expected answer
    • last_persisted_sequence (integer)
    • last_persisted_stamp (rfc3339-date-time)
    • discard (boolean)
  4. What spoofing, unauthorized organizer-replacement or flood controls apply to this scheduling message, as warned in iTIP security considerations?access
    Expected answer
    • authenticated_originator (boolean)
    • organizer_replacement_authorized (boolean)
Artifacts
  • Scheduling messageOne iTIP-style method payload correlated by UID, recurrence id, sequence and stamp time.
b-revision-execution-and-governanceRevision, Execution and Governance3 layers

Baselines and change control, progress and realization, closure, provenance, disclosure, retention and exchange.

l-baseline-and-change-controlBaseline and Change Control2 findings

Frozen reference versions and the controlled record of what changed and why.

f-baseline-snapshot-and-approval

Baseline snapshot and approval

Immutable frozen versions of a plan against which later performance and variance are measured.

Questions
  1. Which elements are frozen in the baseline and which remain live?composition
    Expected answer
    • Frozen element list
    • Live element list
    • Scope statement
  2. Who approved the baseline, and under what rule may the plan be re-baselined?authority
    Expected answer
    • Approver reference
    • Re-baselining rule
    • Threshold triggering re-baseline
  3. How are multiple concurrent baselines distinguished, and which is current?identity
    Expected answer
    • Baseline identifiers
    • Current baseline marker
    • Purpose of each baseline
  4. How is it proven that a stored baseline has not been altered since freezing?security
    Expected answer
    • Content digest
    • Digest algorithm
    • Verification procedure
Artifacts
  • Baseline snapshotImmutable frozen copy of a plan revision with its digest and approval, held as the comparison reference for variance.
f-change-log-and-reason-codes

Change log and reason codes

The controlled record of what changed in a plan, why, on whose authority and at which distinct times.

Questions
  1. At what granularity is a change recorded: whole plan, entry, or individual field?composition
    Expected answer
    • Granularity rule
    • Changed element references
    • Before and after values
  2. Which controlled reason code explains the change, distinguishing correction of an error from genuine re-planning?classification
    Expected answer
    • Reason code
    • Reason code vocabulary reference
    • Free-text justification
  3. Who authorized the change, and was downstream notification required?authority
    Expected answer
    • Authorizing agent
    • Authorization basis
    • Notified party references
  4. Which timestamps record when the change was decided, applied and observed by consumers?temporal
    Expected answer
    • Decision timestamp
    • Application timestamp
    • Observation or ingestion timestamp
Artifacts
  • Plan change logAppend-only sequence of change entries with reason codes, authorities and separated decision, application and observation times.
l-progress-realization-and-closureProgress, Realization and Closure3 findings

Recorded actuals against plan, the acts that realized intentions, and the terminal states of a plan.

f-progress-actuals-and-variance

Progress actuals and variance

Progress recorded against the plan as of a stated status date, and the variance computed against baseline.

Questions
  1. How is progress expressed, and is the measurement method declared rather than assumed?measurement
    Expected answer
    • Progress value
    • Method code such as percent complete or remaining duration
    • Declared method definition
  2. Which actual start and finish dates are recorded, and are dates later than the status date rejected?temporal
    Expected answer
    • Actual start
    • Actual finish
    • Status date
    • Future-actual validation rule
  3. What variance against the baseline is computed, and at which level of the plan?validation
    Expected answer
    • Variance value and unit
    • Baseline reference
    • Aggregation level
  4. As of which status date is the progress statement valid, and who asserted it?provenance
    Expected answer
    • Status date
    • Asserting agent
    • Assertion timestamp
Artifacts
  • Progress update recordPeriodic record of actuals, remaining work and variance as of a status date, stored alongside rather than overwriting the baseline.
f-closure-and-abandonment

Closure and abandonment

Terminal states of a plan, the authority and reason for ending it, and the treatment of residual obligations.

Questions
  1. Which terminal states may a plan reach, and how are they distinguished from one another?lifecycle
    Expected answer
    • Terminal state code list
    • Definition per state
    • Allowed transitions into each
  2. What reason and authority are recorded when a plan is dropped before completion?decision
    Expected answer
    • Closure reason code
    • Deciding agent
    • Decision evidence reference
  3. What happens to open commitments and future occurrences when the plan closes?exception
    Expected answer
    • Residual commitment references
    • Cancellation or transfer action
    • Notified counterparties
  4. May a closed plan be edited, and if not, how are subsequent corrections expressed?constraint
    Expected answer
    • Edit prohibition rule
    • Correction mechanism
    • Successor plan reference
Artifacts
  • Plan closure recordRecord of the terminal state, reason, deciding authority and the disposition of residual commitments and future occurrences.
l-provenance-access-and-exchangeProvenance, Access and Exchange3 findings

Where a plan came from, who may see what, how long it is kept, and how it maps to external vocabularies.

f-plan-provenance-and-attribution

Plan provenance and attribution

The agent and activity that produced a plan version, and the prior plans, templates or forecasts it derives from.

Questions
  1. Which agent, human or software, generated this plan version, and under which activity?provenance
    Expected answer
    • Attributed agent reference
    • Generating activity reference
    • Generation timestamp
  2. From which prior plan, template or forecast is this plan derived?relationship
    Expected answer
    • Derived-from references
    • Derivation kind
    • Transformation description
  3. Is the planning agent autonomous software, and are its identity and version recorded?classification
    Expected answer
    • Agent type code
    • Software name and version
    • Operating human principal
  4. Which upstream instruction or request caused the plan to be created?authority
    Expected answer
    • Triggering request reference
    • Requesting agent
    • Received timestamp
Artifacts
  • Plan provenance graphGraph of attribution, generation, association and derivation relations connecting plan versions, planning agents and executing activities.
f-disclosure-access-and-retention

Disclosure, access and retention

The level of detail each audience may see, the grants that permit it, and how long plan records are kept before authorized disposition.

Questions
  1. At which level of detail is the entry shared: full content, busy-only, or hidden entirely?privacy
    Expected answer
    • Disclosure class code
    • Audience scope
    • Redacted field list
  2. Which grants let a non-owner read or write the plan, and do they apply per entry or per plan?access
    Expected answer
    • Grantee references
    • Permitted operations
    • Grant scope and expiry
  3. How long are plan, schedule and commitment records retained after closure, and under whose records schedule?retention
    Expected answer
    • Retention rule reference
    • Retention trigger and period
    • Authorizing schedule and role dependency
  4. When an entry is deleted, what marker remains so that replicas do not resurrect it?exception
    Expected answer
    • Tombstone marker
    • Tombstone retention window
    • Replication reconciliation rule
  5. Which fields may reveal sensitive location, health or negotiation information and must be redacted in projections?security
    Expected answer
    • Sensitive field list
    • Redaction rule per projection
    • Approving role
Artifacts
  • Disclosure and retention policyThe owner package's binding statement of disclosure classes per audience, access grant rules, retention periods and authorized disposition actions.
f-interoperability-and-exchange-alignment

Interoperability and exchange alignment

Mappings to external calendaring and planning vocabularies, the losses in each direction, and what any conformance claim rests on.

Questions
  1. To which external vocabularies does this model map, and which elements are lossy in each direction?interoperability
    Expected answer
    • Target vocabulary identifiers and versions
    • Element-level mapping table
    • Lossy construct list per direction
  2. Does an export and re-import round trip preserve identity, revision counter and occurrence overrides?validation
    Expected answer
    • Round-trip test result
    • Preserved and lost element lists
    • Test fixture reference
  3. What evidence supports a conformance claim, as distinct from a mere alignment?evidence
    Expected answer
    • Claim statement
    • Test evidence reference
    • Scope and exclusions of the claim
  4. How are locally required fields carried without breaking a receiving implementation?constraint
    Expected answer
    • Extension namespace
    • Ignore-unknown rule
    • Criticality marking convention
Artifacts
  • Alignment and mapping tableElement-level mapping between this model and each external vocabulary, annotated with direction, loss and round-trip test evidence.

Publication holds

  • Source and live-version verification is incomplete: every one of the 15 base sources plus the two newly imported grok sources (RFC 9253, P-Plan 1.1) must have its URL resolved and its version pin confirmed before publication, with particular attention to the IANA tz database release claim (2026c, 8 July 2026) and the schema.org Schedule entry, which is a live vocabulary pinned only by an access date.
  • GAO-16-89G was confirmed from the product page and indexed text only; the full PDF was not machine-extracted. f-schedule-integrity-and-quality and the ten-best-practices framing must not be published with quoted or enumerated practice wording until verified against the source document.
  • NARA GRS 5.1 item number and disposition wording were not machine-extracted because the PDF returned as binary. The retention questions may be published only as structure; no specific GRS item citation may be asserted until the wording is verified.
  • Multi-profile validation is not complete. The merged model was exercised against calendaring, project-scheduling and care-intention profiles; it must also be validated against an autonomous software-agent planning profile and at least one non-US records-retention profile before release, since the retention layer currently rests on a single jurisdiction.
  • ISO 21502 must not appear anywhere in the published draft as a normative baseline authority; it is paywalled and available at catalogue level only in the grok pack and was deliberately not imported as a source.

Deferred research

  • RFC 7529 (rscale and skip) as a fetched primary source for non-Gregorian recurrence, which both packs reach only indirectly through JSCalendar or the OWL-Time temporal reference system concept.
  • RFC 7953 VAVAILABILITY against the base f-duration-effort-and-working-calendar finding, to determine whether availability components subsume, conflict with, or complement the working-calendar model; grok records it as an explicit omission.
  • A non-US retention authority (EU storage-limitation text and at least one non-US national records schedule) to close the single-jurisdiction gap the base itself flags in its retention checklist.
  • Hierarchical task network decomposition and simple temporal networks with uncertainty, to decide whether they are an extension point on f-planned-action-specification or a separate sibling model.
  • ANSI/EIA-748 and ISO 21508 for the baseline and earned-value boundary, which both packs could only assert at catalogue level or exclude for lack of fetchable text.
  • The iTIP organizer-sole-write model versus a scheduler-maintained integrated schedule fed by contributor updates: both authority models are recorded as a conflict but no reconciliation rule is evidenced, and the newly imported scheduling-message finding makes it operationally live.