Draft · revised 28 August 2026. This document circulates as part of the federated data-sharing bundle; every document in that bundle carries the same revision date, so a reader holding a mixed set can tell at a glance that one of them is stale.
What this is. One instrument that replaces the bilateral data-sharing agreement for unclassified data. It has two halves that are signed by different people at different times:
- Part I — the Declaration. The data owner fills this in and publishes it. Unilateral: nobody negotiates it, nobody countersigns it, and it is complete the moment the owner adopts it. It says what the owner releases, who may take it, how a recipient must handle it, and how the owner takes it back.
- Part II — the Accession. A recipient who wants the data fills in this half and returns it. One act, no counter-draft. Acceding accepts Part I exactly as published. Editing Part I is not acceding; it is asking for a different declaration, which the owner is free to write or refuse.
Acceding is an undertaking, not a receipt. The recipient binds itself, under signature by a person mandated to give it, to every handling term in section 5 — what the data may be used for, whether it may be passed on, keeping its origin attached, protecting it in proportion to the sensitivity the owner has stated, keeping an access record, reporting an incident, and what happens on withdrawal. What this instrument removes is the negotiation over those terms, never the terms themselves.
Part I serves every recipient that accedes to it. The tenth recipient costs what the first cost.
Template status. This is the template for release under paragraph 21 of the Framework Policy on Data Access and Release in Federated Mission Environments, which circulates with it. To use it: take a copy, fill the placeholders, and delete this block and the one below.
Unclassified only. This instrument is for data its owner has determined to be unclassified. It does not release classified information, and it is not a substitute for a Security Agreement, a Security Assurance, or any national classified-release process. Where a would-be flow is classified, this instrument does not apply and does not claim to.
Relationship to a bilateral data-sharing charter. A negotiated bilateral charter remains available, and is the right instrument where a relationship genuinely needs bilateral terms — reciprocal obligations, jointly-owned data, negotiated liability. This declaration is the default for the ordinary case: one owner opening its own data on terms it sets. Do not sign both for the same data.
| Declared by | [DECLARING ORGANIZATION — legal or official name] |
|---|---|
| Declaration identifier | [SHORT STABLE ID, e.g. REL-2026-001] |
| Version | 1.0 |
| Adopted | [DATE] |
| Published at | [WHERE THIS IS PUBLISHED] |
| Point of contact | [ROLE OR OFFICE — a role, not a named individual] |
I, the declaring organization, own the data described in section 2 and have determined it to be unclassified. I release it on the terms below to any recipient that accedes under Part II. I make this declaration on my own authority. It commits no one else, and it releases no data but my own.
| Field | Value |
|---|---|
| Data assets covered | [NAME THE STREAMS / PRODUCT LINES / DATASETS. Name the asset, not every message.] |
| Producing systems | [WHICH SYSTEMS ORIGINATE THIS DATA] |
| Labels carried | fidelity: [notional / simulated / real] · context: [experiment / exercise / operational] · access: [community / organization / controlled] |
| Update rate and volume, typical | [SO A RECIPIENT CAN SIZE FOR IT] |
| Explicitly not released | [ANYTHING A READER MIGHT REASONABLY ASSUME IS INCLUDED AND IS NOT] |
| Sensitivity of what is released | [STATE IT IN ONE OR TWO SENTENCES: what harm would follow from this data reaching someone it was not released to, and what about it is sensitive — for example what it would reveal about a capability, a position, an intention, or how it was obtained. This is what handling term 4 makes the recipient protect proportionately, so a recipient cannot calibrate its handling without it. If the honest answer is "little or none", say that — it is a legitimate answer, and it lowers the recipient's burden accordingly.] |
Alliance membership, nationality, and partner status are not conditions. If a condition here has the effect of admitting allies and excluding partners without saying why in operational terms, it is the wrong condition — rewrite it or delete it.
| Field | Value |
|---|---|
| Environment | [THE FEDERATED MISSION ENVIRONMENT / BACKBONE THIS DATA IS PUBLISHED INTO] |
| Admission bar a recipient must already hold | [THE ENVIRONMENT'S OWN ADMISSION REQUIREMENTS — this declaration adds to them, never replaces them] |
| Namespace / channel the data arrives on | [WHERE A RECIPIENT SUBSCRIBES] |
These are the whole of what a recipient agrees to. They are deliberately short. Anything not on this list is not required, and a recipient should not be asked for it.
| Field | Value |
|---|---|
| This declaration stands until | [DATE, or "withdrawn"] |
| Accessions expire after | [PERIOD — an accession that is not renewed lapses; renewal is a decision, not a default] |
| Withdrawal of the whole declaration | The declarant may withdraw at any time, for any reason, without notice period. Withdrawal is published at the location in the header. |
| Withdrawal of a single accession | The declarant may withdraw any single recipient's accession at any time, for any reason, without affecting any other recipient. |
| How withdrawal takes effect | At the identity and key layer of the environment — the recipient's grant is revoked and, for encrypted data, the key is changed. It does not wait on a notice period or a termination clause. |
Signed for the declaring organization
Fill in, sign, return to the contact in the Part I header. Do not edit Part I. Returning this form with Part I altered is not an accession.
| Acceding organization | [LEGAL OR OFFICIAL NAME] |
|---|---|
| Acceding to declaration | [DECLARATION IDENTIFIER], version [VERSION] |
| Identity in the environment | [THE ORGANIZATION'S IDENTITY / SLOT / ANCHOR IN THE ENVIRONMENT NAMED IN SECTION 4] |
| Point of contact | [ROLE OR OFFICE] |
The acceding organization:
Signed for the acceding organization
An accession is not in force until it is recorded. Recording it means:
| Step | What happens |
|---|---|
| 1. Record | The accession is entered in the environment's register of declarations and accessions, against the declaration identifier. |
| 2. Enact | An access grant is issued to the acceding organization's identity for the assets in section 2, with the expiry from section 6 and this declaration identifier as its recorded reason. |
| 3. Confirm | The declarant tells the acceding organization the grant is live. |
| 4. Review | At expiry, the grant lapses unless the declarant renews it. Lapse is the default. |
Withdrawal reverses steps 2 and 1, in that order: revoke the grant (and change the key, for encrypted assets) first, then mark the accession withdrawn in the register.