Render Unstructured Content in StratML

Render the supplied source content in StratML Part 1 format conforming to ISO 17469-1. Preserve the intentions expressed in the source as faithfully as possible. Do not silently invent goals, objectives, stakeholders, values, or other substantive content. Where structure must be inferred from narrative material, make reasonable inferences only when necessary and document significant inferences in the appropriate OtherInformation elements. Apply these conventions: • Use nouns or noun phrases for Goal and Objective Names. • Begin Goal and Objective Descriptions with active verbs expressing the intended result. • Distinguish objectives (intended results) from activities, methods, organizations, topics, and resources. • Identify stakeholders explicitly mentioned or reasonably implied by the source and classify them appropriately as Person, Organization, or Generic_Group. • Place stakeholders at the plan, goal, or objective level where their roles are most directly relevant. • Capture important source detail that does not fit naturally elsewhere in OtherInformation rather than discarding it. • Preserve useful source URLs and references. • Assign globally unique identifiers to elements requiring identifiers. • Provide SequenceIndicators for Goals and Objectives. • Do not include HTML markup in the XML. • Do not fabricate facts merely to populate optional elements. • Preserve distinctions, qualifications, uncertainties, inconsistencies, and limitations rather than silently resolving them. If the source is lengthy, provide the XML in manageable sequential segments so it can be reviewed and validated incrementally. Begin with the opening elements, organization, vision, mission, values, and first goal. Wait for “Next” before continuing. Before finalizing, check XML well-formedness and conformance to the supplied or referenced ISO 17469-1 schema.

Render or extend the supplied source content in StratML Part 2 format using the applicable StratML Part 2 schema. Preserve the source faithfully. Do not invent performance claims, targets, baselines, dates, actual results, stakeholder roles, or quantitative values merely to populate the schema. In addition to the applicable Part 1 conventions: • Identify stakeholder roles relevant to each objective. • Represent inputs, processing, outputs, outcomes, and other value-chain information where supported by the source. • Derive performance indicators only from measurable results stated or reasonably supported by the source. • Use UnitOfMeasurement only for quantitative indicators. • Use a short noun or noun phrase for MeasurementDimension. • When a numeric value is supported, capture it in NumberOfUnits. • Preserve useful percentage or explanatory wording in the Target or Actual Description while also capturing machine-processable numeric values where possible. • Distinguish targets from actual results. • When the source provides a baseline actual result, preserve its applicable date. • Do not manufacture missing targets, baselines, dates, or actual values. • For qualitative indicators, do not fabricate quantitative units. • Document calculations, conversions, ambiguities, source inconsistencies, inferred values, and other material qualifications in OtherInformation. If percentages, rates, or ratios can legitimately be converted into NumberOfUnits from other source values, calculate them when useful, preserve the original percentage or rate in the Description, and document the calculation in OtherInformation. If the source is lengthy or structurally complex, provide the XML in manageable sequential segments and wait for “Next” before continuing. Before finalizing, check XML well-formedness and conformance to the supplied Part 2 schema.

Review the complete StratML draft against both the source material and the applicable StratML schema. Check particularly for missing or duplicated goals, objectives, stakeholders, indicators, or source information; Goal and Objective Names that are not noun phrases; Descriptions that fail to express intended results with active verbs; activities or methods incorrectly represented as objectives; stakeholder roles represented at inappropriate levels; missing or duplicate SequenceIndicators; identifiers that are not globally unique; unsupported AI-generated assertions; source qualifications, inconsistencies, or uncertainties that have been lost; and XML well-formedness or schema-validity problems. Do not rewrite valid content merely for stylistic preference. Recommend only corrections that materially improve fidelity, validity, completeness, interoperability, or clarity.