GEOS-FN-007 — Metadata & Disclosure Requirements (Foundational Numeracy)

GEOS-FN-007 — Metadata & Disclosure Requirements (Foundationa Numeracy)

Version: 0.01 Status: Normative Standard

0. Interpretive Basis and Certification Intent ————————————————--

GEOS-FN-007 defines the metadata requirements that an Outcom Signal Portfolio (OSP) MUST satisfy in order to be eligible for certification by a GEOSor™ as a GEOS Certified Outcome Signal Portfolio (GeOSP™) for Foundational Numeracy.

This standard:

• constrains certifiable artifacts only;

• defines no disclosure obligations on any role;

• does not require public disclosure of any data or metadata; and

• specifies metadata solely to enable auditability, comparability, and contestability of certified artifacts.

Certification under this standard is voluntary and applies only to the OSP submitted for assessment.

1. Purpose ————--

The purpose of this standard is to ensure that any GeOSP™ includes sufficient, structured metadata to:

• support conformity assessment by a GEOSor™;

• enable reproducibility and contestability of certified signals;

• allow authorized counterparties to interpret certified signals correctly; and

• preserve inter-temporal and cross-jurisdictional comparability.

This standard does not prescribe who may access metadata, nor under what contractual or confidentiality terms such access may occur.

2. Scope ————

This standard applies to:

• metadata associated with Sentinel signals included in an OSP; and

• metadata associated with the portfolio as a whole.

This standard does not apply to:

• learner-level data;

• raw Layer A data;

• internal operational data not referenced by certified signals; or

• any disclosure mechanism external to GEOS certification.

3. Certification Boundary —————————--

An OSP is eligible for certification as a GeOSP™ only if all metadata required by this standard:

• is included within the artifact submitted for assessment; and

• remains internally consistent with the signals and transformations defined in GEOS-FN-003 and GEOS-FN-004

No metadata element defined in this standard is required to be disclosed outside the GeOSP™ artifact itself, except as permitted under separate agreements.

4. Required Portfolio-Level Metadata —————————————-

A certifiable OSP MUST include the following portfolio-level metadata elements:

4.1 Portfolio Identity

• unique portfolio identifier;

• GEOS standard version references;

• Foundational Numeracy domain identifier (GEOS-FN);

• reporting period(s) covered.

4.2 Jurisdictional Scope

• list of jurisdictions included in the portfolio;

• explicit declaration of whether aggregation is single-jurisdiction or cross-jurisdiction; and

• confirmation that any funding claim relying on the portfolio applies exclusively to the same set of jurisdictions represented.

4.3 Data Provenance Summary

• identification of the data stream(s) used;

• reference to conformity with GEOS data stream requirements; and

• declaration of reference implementation use, where applicable.

5. Required Signal-Level Metadata ————————————-

For each Sentinel signal included in a certifiable OSP, the artifact MUST include:

5.1 Construct Attribution

• construct family reference (per GEOS-FN-002;

• status or progress classification; and

• signal family reference (per GEOS-FN-003.

5.2 Construction Specification

• Layer B aggregation definition;

• Layer C transformation logic;

• normalization rules applied; and

• treatment of missing or sparse data.

5.3 Temporal Definition

• measurement window(s);

• baseline and follow-up specification (where applicable); and

• exposure or instructional time proxy used.

5.4 Volatility Declaration

• self-declared volatility characteristics;

• declared thresholds for interpretive caution; and

• consistency of volatility handling across reporting periods.

6. Audit and Reproducibility Metadata —————————————--

A certifiable OSP MUST include metadata sufficient to allow a GEOSor™ to:

• reproduce all signals from Layer A data under audit;

• verify immutability of inputs and transformations; and

• confirm internal consistency across portfolio elements.

This standard defines metadata requirements only and does not define audit procedures.

7. Disclosure Semantics —————————

7.1 Internal Completeness

All metadata required by this standard MUST be internally present within the OSP artifact submitted for certification.

7.2 External Availability

This standard does not require disclosure of any metadata to any party.

Where an OSP or GeOSP™ is made available to authorized counterparties, metadata MAY be shared under terms external to GEOS Standards.

8. Explicit Non-Requirements ——————————--

This standard does not require:

• public disclosure of any metadata;

• disclosure of learner-level data;

• disclosure of raw Layer A data;

• disclosure of Layer B aggregates outside audit; or

• disclosure of transformation code or implementation artifacts.

9. Relationship to Other GEOS Standards ——————————————-

This standard is normative only when applied in conjunction with:

• GEOS-FN-001 (Outcomes Framework)

• GEOS-FN-002 (Outcome Domain Taxonomy)

• GEOS-FN-003 (Sentinel Signal Families); an

• GEOS-FN-004 (Signal Construction & Transformation Rules)

10. Versioning ——————

Metadata requirements defined herein are subject to GEOS versioning rules.

Changes to required metadata fields MUST preserve backward interpretability of previously certified GeOSPs™ wherever feasible.

End of GEOS-FN-007