Dialogue Director V1.1 — Skill Director Integration Contract
Review draft. This source page has not completed website editorial and release-specific verification.
Status
Section titled “Status”APPROVED FOR FUTURE DIALOGUE DIRECTOR V1.1
DO NOT IMPLEMENT UNTIL SKILL DIRECTOR V1 PUBLIC CONTRACT IS STABLE.
This document defines the intended replacement of Dialogue-specific Skill authority with Skill Director.
1. Goal
Section titled “1. Goal”Dialogue Director V1.1 shall use Skill Director as the authoritative source of character Skill state.
Dialogue Director remains the narrative gameplay orchestrator.
Skill Director owns Skill state and progression.
Probability Director owns random resolution.
2. Optional Dependency
Section titled “2. Optional Dependency”Dialogue Director core shall not gain a mandatory Skill Director dependency.
Use:
DialogueDirectorSkillBridge
The bridge depends on:
- Dialogue Director
- Skill Director
and integrates with Dialogue’s existing Probability systems as required.
3. Skill Identity
Section titled “3. Skill Identity”Dialogue authoring uses exact concrete:
Skill.*
identities.
Dialogue must not create or retain an independent authoritative Skill namespace.
4. Existing Dialogue Character Skill System
Section titled “4. Existing Dialogue Character Skill System”Before V1.1 implementation, audit the current Dialogue Character Skill implementation.
Architectural destination:
Skill Director becomes the single authoritative Skill system.
Do not permanently maintain two competing Skill authorities.
Preferred strategy while production content remains limited:
clean migration/deprecation.
If authored assets require conversion, provide an explicit migration path.
5. Skill Gates
Section titled “5. Skill Gates”Dialogue V1.1 shall support deterministic Skill conditions.
Example:
Skill.Psyche.Authority >= 6
The bridge queries:
Effective Skill Value
No Probability roll occurs.
Supported numeric comparisons should follow the established Dialogue condition model.
6. Skill Checks
Section titled “6. Skill Checks”Existing Dialogue Probability skill-check architecture remains.
Conceptually:
Dialogue -> Skill Director Effective Value -> Probability Director Resolution -> Dialogue Success/Failure branch
Skill Director does not roll.
Probability Director does not own Skill state.
7. Positive/Negative Modifiers
Section titled “7. Positive/Negative Modifiers”Dialogue always queries the current Effective Skill value.
Therefore modifiers caused by:
- Character State;
- Inventory/equipment;
- Thoughts;
- other approved sources
automatically affect Dialogue gates/checks without Dialogue understanding those systems.
8. Dialogue XP Actions
Section titled “8. Dialogue XP Actions”Dialogue V1.1 shall support actions equivalent to:
Grant Global Skill XP
Grant Per-Skill XP
Per-Skill action requires an exact concrete Skill.* identity.
Dialogue supplies the XP request.
Skill Director determines:
- threshold crossings;
- permanent increases;
- Skill Points awarded;
- committed events.
9. No Dialogue Level-Up Logic
Section titled “9. No Dialogue Level-Up Logic”Dialogue must not:
- calculate XP thresholds;
- directly increment XP-derived Skill levels;
- manage Unspent Skill Points;
- own progression tables.
Those belong to Skill Director.
10. Dialogue UI
Section titled “10. Dialogue UI”Future Dialogue/UI presentation may display Skill-gate/check information supplied by Dialogue and Skill integration.
UI does not query or mutate hidden alternate Skill state.
11. Probability Compatibility
Section titled “11. Probability Compatibility”V1.1 must preserve the existing approved Probability Director architecture, including:
- stream ownership;
- DecisionKey semantics;
- deterministic behavior;
- resolution rules;
- persistence;
- anti-save-scum behavior.
Only the authoritative source of Skill value changes.
12. Migration Gate
Section titled “12. Migration Gate”Dialogue V1.1 is not complete until:
- legacy Skill ownership is audited;
- migration behavior is defined;
- existing Skill check assets are validated/migrated;
- Skill gates use
Skill.*; - Probability-backed Skill checks use Skill Director;
- XP actions are covered;
- no second authoritative Skill state remains.
13. Version Boundary
Section titled “13. Version Boundary”Dialogue Director V1 may finish on its existing architecture.
Skill Director integration is explicitly Dialogue Director V1.1 scope.
Do not destabilize the nearly complete Dialogue V1 solely to introduce Skill Director early.