Forge Intelligence

LCDL overlay: Parenting and Child Development Support 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.parenting-child-development.understand_development_context intelligence_parenting_child_development_understand_development_context_v1 artifact.life.parenting-child-development.child_and_family_context validator.life.parenting-child-development.02_age_and_ability_appropriateness
capability.life.parenting-child-development.design_family_routine intelligence_parenting_child_development_design_family_routine_v1 artifact.life.parenting-child-development.family_routine validator.life.parenting-child-development.01_safeguarding_and_immediate_danger, validator.life.parenting-child-development.02_age_and_ability_appropriateness, validator.life.parenting-child-development.03_nonviolent_discipline
capability.life.parenting-child-development.analyze_behavior_context intelligence_parenting_child_development_analyze_behavior_context_v1 artifact.life.parenting-child-development.behavior_observation_log validator.life.parenting-child-development.01_safeguarding_and_immediate_danger, validator.life.parenting-child-development.02_age_and_ability_appropriateness, validator.life.parenting-child-development.03_nonviolent_discipline
capability.life.parenting-child-development.plan_positive_support intelligence_parenting_child_development_plan_positive_support_v1 artifact.life.parenting-child-development.positive_support_plan validator.life.parenting-child-development.01_safeguarding_and_immediate_danger, validator.life.parenting-child-development.02_age_and_ability_appropriateness, validator.life.parenting-child-development.03_nonviolent_discipline
capability.life.parenting-child-development.support_learning_play intelligence_parenting_child_development_support_learning_play_v1 artifact.life.parenting-child-development.learning_and_play_plan validator.life.parenting-child-development.02_age_and_ability_appropriateness
capability.life.parenting-child-development.coordinate_school_care intelligence_parenting_child_development_coordinate_school_care_v1 artifact.life.parenting-child-development.school_or_care_meeting_brief validator.life.parenting-child-development.01_safeguarding_and_immediate_danger, validator.life.parenting-child-development.02_age_and_ability_appropriateness, validator.life.parenting-child-development.03_nonviolent_discipline
capability.life.parenting-child-development.recognize_safeguarding_concerns intelligence_parenting_child_development_recognize_safeguarding_concerns_v1 artifact.life.parenting-child-development.safeguarding_concern_and_escalation_record, artifact.life.parenting-child-development.escalation_route validator.life.parenting-child-development.01_safeguarding_and_immediate_danger, validator.life.parenting-child-development.02_age_and_ability_appropriateness, validator.life.parenting-child-development.03_nonviolent_discipline

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.parenting-child-development.child_and_family_context ../schemas/artifacts/parenting-child-development.schema.json#/$defs/child_and_family_context subject_or_scope, purpose, facts_or_observations, preferences_and_constraints, source_refs, uncertainty, date_range, next_questions restricted
artifact.life.parenting-child-development.family_routine ../schemas/artifacts/parenting-child-development.schema.json#/$defs/family_routine objective, scope, steps, dependencies, constraints, owners, timing, contingencies, review_triggers restricted
artifact.life.parenting-child-development.behavior_observation_log ../schemas/artifacts/parenting-child-development.schema.json#/$defs/behavior_observation_log entries, entry_ids, owners, status, source_refs, updated_at restricted
artifact.life.parenting-child-development.positive_support_plan ../schemas/artifacts/parenting-child-development.schema.json#/$defs/positive_support_plan objective, scope, steps, dependencies, constraints, owners, timing, contingencies, review_triggers restricted
artifact.life.parenting-child-development.learning_and_play_plan ../schemas/artifacts/parenting-child-development.schema.json#/$defs/learning_and_play_plan objective, scope, steps, dependencies, constraints, owners, timing, contingencies, review_triggers restricted
artifact.life.parenting-child-development.school_or_care_meeting_brief ../schemas/artifacts/parenting-child-development.schema.json#/$defs/school_or_care_meeting_brief purpose, scope, stakeholders, requirements, constraints, assumptions, success_criteria restricted
artifact.life.parenting-child-development.escalation_route ../schemas/artifacts/parenting-child-development.schema.json#/$defs/escalation_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.parenting-child-development.safeguarding_concern_and_escalation_record ../schemas/artifacts/parenting-child-development.schema.json#/$defs/safeguarding_concern_and_escalation_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.parenting-child-development.01_safeguarding_and_immediate_danger policy_and_classifier hybrid blocker escalate
validator.life.parenting-child-development.02_age_and_ability_appropriateness rule_and_human_review human_review blocker escalate
validator.life.parenting-child-development.03_nonviolent_discipline policy hybrid major repair
validator.life.parenting-child-development.04_observation_versus_hypothesis_versus_professional_conclusion provenance 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/parenting-child-development.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/parenting-child-development.yaml
  • Cases defined: 7
  • Capabilities under test: 7