feat(ATA06-10-00): export TLAR Dimensions YAML/JSON for SSOT#76
Draft
feat(ATA06-10-00): export TLAR Dimensions YAML/JSON for SSOT#76
Conversation
Add SSOT-ready YAML and JSON exports for TLAR dimension requirements (TLAR-DIM-001 through TLAR-DIM-004) under LC02_SYSTEM_REQUIREMENTS. Includes: meta (ATA/KNOT/KNU traceability), 4 requirements with datum_definition, config_state, tolerance, source_ref, allocated_to. Update SUBJECT_MANIFEST.yaml: LC02 artifacts 1→3, completion 70→90%. Co-authored-by: AmedeoPelliccia <164860269+AmedeoPelliccia@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Export YAML/JSON for SSOT with additional fields
feat(ATA06-10-00): export TLAR Dimensions YAML/JSON for SSOT
Feb 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add machine-readable SSOT exports for the four normalized TLAR dimension requirements (TLAR-DIM-001 through -004) under
LC02_SYSTEM_REQUIREMENTS, with full KNOT/KNU traceability.New files
ATA06-10-00_TLAR_DIMENSIONS.yaml— canonical SSOT source withssot_requirements.meta(ATA ref, parent KNOT/KNU, downstream KNUs) andrequirements[]array carryingdatum_definition,config_state,tolerance,source_ref,allocated_toper requirementATA06-10-00_TLAR_DIMENSIONS.json— equivalent JSON for tooling/API consumers; validated identical to YAMLUpdated
SUBJECT_MANIFEST.yaml— LC02 artifact count 1→3, completion 70%→90%Structure
All four requirements (LOA, BWB span, max height, centerbody width) have TBD limits/tolerances per the current LC02 maturity level.
Original prompt
ATA 06-10-00 — ZONING — TLAR Dimensions (normalizado) → export YAML/JSON para SSOT
ATA: 06 / 10 / 00 (DIMENSIONS AND AREAS → ZONING → GENERAL)
Lifecycle: LC02_SYSTEM_REQUIREMENTS
Artifact Domain: SSOT (REQ)
KNOT→KNU:
KNOT-ATA06-10-00-001→KNU-ATA06-10-00-001-REQ-001Traceability: TLAR-DIM-* (LC02) →
KNU-...-DES-002(BWB Geometry) →KNU-...-DES-001(Zoning Scheme/Register)A continuación te devuelvo la misma tabla en YAML y JSON, incorporando los campos mínimos extra (
Datum/Definition,Config/State,Tolerance,SourceRef,AllocatedTo) + ATA y links KNOT/KNU, lista para pegar en tu SSOT.YAML (SSOT-ready)
JSON (equivalente, SSOT-ready)
{ "ssot_requirements": { "meta": { "ata": { "chapter": "06", "section": "10", "subject": "00", "title": "TLAR Dimensions — Normalized" }, "domain": "SSOT", "lifecycle_owner": "LC02_SYSTEM_REQUIREMENTS", "parent_knu_id": "KNU-ATA06-10-00-001-R... </details> <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey).