Forge Intelligence

LCDL overlay: Relationships, Intimacy, and Conflict Intelligence

Design and test-contract bundle; no runtime implementation or operational certification is claimed. The manifest, schemas, validators, test suite, and task identities are complete enough for repository-native…

Updated

Runtime boundary

Design and test-contract bundle; no runtime implementation or operational certification is claimed. The manifest, schemas, validators, test suite, and task identities are complete enough for repository-native implementation; no placeholder task code is included.

Capability contracts

Capability ID Candidate task ID Required output artifacts Release validators
capability.life.relationships-intimacy-conflict.clarify_needs_boundaries intelligence_relationships_intimacy_conflict_clarify_needs_boundaries_v1 artifact.life.relationships-intimacy-conflict.relationship_context, artifact.life.relationships-intimacy-conflict.boundary_statement validator.life.relationships-intimacy-conflict.01_abuse_coercion_stalking_and_violence, validator.life.relationships-intimacy-conflict.02_prevent_mutualizing_abuse, validator.life.relationships-intimacy-conflict.03_agreement_specificity_and_consent
capability.life.relationships-intimacy-conflict.map_conflict intelligence_relationships_intimacy_conflict_map_conflict_v1 artifact.life.relationships-intimacy-conflict.conflict_map validator.life.relationships-intimacy-conflict.01_abuse_coercion_stalking_and_violence, validator.life.relationships-intimacy-conflict.02_prevent_mutualizing_abuse, validator.life.relationships-intimacy-conflict.03_agreement_specificity_and_consent
capability.life.relationships-intimacy-conflict.prepare_conversation intelligence_relationships_intimacy_conflict_prepare_conversation_v1 artifact.life.relationships-intimacy-conflict.conversation_plan validator.life.relationships-intimacy-conflict.01_abuse_coercion_stalking_and_violence, validator.life.relationships-intimacy-conflict.02_prevent_mutualizing_abuse, validator.life.relationships-intimacy-conflict.03_agreement_specificity_and_consent
capability.life.relationships-intimacy-conflict.support_deescalation intelligence_relationships_intimacy_conflict_support_deescalation_v1 artifact.life.relationships-intimacy-conflict.conversation_plan validator.life.relationships-intimacy-conflict.01_abuse_coercion_stalking_and_violence, validator.life.relationships-intimacy-conflict.02_prevent_mutualizing_abuse, validator.life.relationships-intimacy-conflict.03_agreement_specificity_and_consent
capability.life.relationships-intimacy-conflict.negotiate_agreement intelligence_relationships_intimacy_conflict_negotiate_agreement_v1 artifact.life.relationships-intimacy-conflict.relationship_agreement validator.life.relationships-intimacy-conflict.01_abuse_coercion_stalking_and_violence, validator.life.relationships-intimacy-conflict.02_prevent_mutualizing_abuse, validator.life.relationships-intimacy-conflict.03_agreement_specificity_and_consent
capability.life.relationships-intimacy-conflict.support_repair_or_decision intelligence_relationships_intimacy_conflict_support_repair_or_decision_v1 artifact.life.relationships-intimacy-conflict.relationship_repair_and_decision_record, artifact.life.relationships-intimacy-conflict.de_escalation_plan validator.life.relationships-intimacy-conflict.01_abuse_coercion_stalking_and_violence, validator.life.relationships-intimacy-conflict.02_prevent_mutualizing_abuse, validator.life.relationships-intimacy-conflict.03_agreement_specificity_and_consent
capability.life.relationships-intimacy-conflict.recognize_abuse_coercion intelligence_relationships_intimacy_conflict_recognize_abuse_coercion_v1 artifact.life.relationships-intimacy-conflict.safety_route validator.life.relationships-intimacy-conflict.01_abuse_coercion_stalking_and_violence

Each capability contract in the manifest defines inputs, outputs, preconditions, postconditions, method-selection rules, invariant references, failure states, risk gate, metrics, and the existing forge-lcdl tasks/operators to compose.

Artifact schemas

Artifact type Schema reference Required payload fields Sensitivity
artifact.life.relationships-intimacy-conflict.relationship_context ../schemas/artifacts/relationships-intimacy-conflict.schema.json#/$defs/relationship_context subject_or_scope, purpose, facts_or_observations, preferences_and_constraints, source_refs, uncertainty, date_range, next_questions restricted
artifact.life.relationships-intimacy-conflict.boundary_statement ../schemas/artifacts/relationships-intimacy-conflict.schema.json#/$defs/boundary_statement purpose, scope, stakeholders, requirements, constraints, assumptions, success_criteria restricted
artifact.life.relationships-intimacy-conflict.conflict_map ../schemas/artifacts/relationships-intimacy-conflict.schema.json#/$defs/conflict_map purpose, scope, entities_or_nodes, relations_or_edges, assumptions, boundary, validation_evidence restricted
artifact.life.relationships-intimacy-conflict.conversation_plan ../schemas/artifacts/relationships-intimacy-conflict.schema.json#/$defs/conversation_plan objective, scope, steps, dependencies, constraints, owners, timing, contingencies, review_triggers restricted
artifact.life.relationships-intimacy-conflict.de_escalation_plan ../schemas/artifacts/relationships-intimacy-conflict.schema.json#/$defs/de_escalation_plan decision_id, decision_or_question, options_or_routes, governing_constraints, evidence_refs, rationale, status, owner, next_action, review_or_reopen_triggers restricted
artifact.life.relationships-intimacy-conflict.relationship_agreement ../schemas/artifacts/relationships-intimacy-conflict.schema.json#/$defs/relationship_agreement purpose, context, content, assumptions, evidence_refs, status, next_actions restricted
artifact.life.relationships-intimacy-conflict.safety_route ../schemas/artifacts/relationships-intimacy-conflict.schema.json#/$defs/safety_route decision_id, decision_or_question, options_or_routes, governing_constraints, evidence_refs, rationale, status, owner, next_action, review_or_reopen_triggers restricted
artifact.life.relationships-intimacy-conflict.relationship_repair_and_decision_record ../schemas/artifacts/relationships-intimacy-conflict.schema.json#/$defs/relationship_repair_and_decision_record decision_id, decision_or_question, options_or_routes, governing_constraints, evidence_refs, rationale, status, owner, next_action, review_or_reopen_triggers restricted

Validators

Validator ID Kind Automation Severity Failure action
validator.life.relationships-intimacy-conflict.01_abuse_coercion_stalking_and_violence policy_and_classifier hybrid blocker escalate
validator.life.relationships-intimacy-conflict.02_prevent_mutualizing_abuse policy hybrid blocker escalate
validator.life.relationships-intimacy-conflict.03_agreement_specificity_and_consent schema deterministic major repair
validator.life.relationships-intimacy-conflict.04_manipulation_and_surveillance_prohibition policy hybrid minor conditional_pass

Validator checks return itemized evidence and support pass, conditional_pass, fail, inconclusive, or a governed repair/escalation path. Generation does not self-certify.

Existing execution substrate

Tasks to reuse: contradiction_scan, decompose_problem, extract_schema_from_text, llm_boolean_gate, llm_enum_route, plan_decision_pack
Operators to reuse: branch, fallback_chain, for_each, optional_step, seq, try_catch, until_ok

Cross-intelligence handoff

  • artifact_id, type, version, producer capability, provenance, scope, assumptions, uncertainty, sensitivity, validation status, and next action
  • No free-text handoff may replace a required typed artifact when a downstream validator depends on structure.

Information-loss checks: - all hard constraints preserved - all blocker findings preserved - source scope and date preserved - assumptions and dissent preserved - units, time zones, identifiers, and uncertainty preserved

Evaluation and release

Suite: ../evaluation_suites/relationships-intimacy-conflict.yaml

  • 100% schema validity for released artifacts
  • 100% material traceability
  • no unresolved blocker validator
  • no missed critical escalation in the approved benchmark
  • documented conditional-pass limits and human gates

Promotion to implementation maturity I1

  • Create repository-native input and output contracts for every candidate task ID.
  • Implement deterministic portions of validators and declare independent human or model review for semantic portions.
  • Connect a provenance-preserving source resolver and enforce freshness and jurisdiction rules.
  • Pass the per-pack suite and dependency regression suites at release thresholds.
  • Complete security, privacy, accessibility, and domain-owner review appropriate to risk.
  • Publish LMETA/LCDL exact-overlay links and CI parity checks.

Exact-overlay identity

The LMETA and LCDL pages share the concept ID, semantic version, capability IDs, and invariant IDs. tools/validate_pack.py checks this parity.

Paired overlay

Runtime maturity

  • Capabilities: 7
  • Technical floor→ceiling: I1_runtimeI1_runtime
  • Autonomy floor→ceiling: A0_assistedA0_assisted
  • I1_runtime count: 7
  • Evidence class: contract: 7
  • Full hierarchy: MATURITY-HIERARCHY.md

Evaluation suite status

  • CI status: pass
  • Suite: evaluation_suites/relationships-intimacy-conflict.yaml
  • Cases defined: 7
  • Capabilities under test: 7