\/<\/p>Specification<\/a>\/<\/p>Conformance<\/b> Conformance is a tested scope, stated with its evidence.<\/h1> Five profiles define what each kind of implementation must do; four levels define how far that has been shown. A level is reached only with the evidence the profile names.<\/p> Read the specification<\/a>Contribute<\/a> Functions<\/dt>12<\/dd> State machines<\/dt>11<\/dd> Objects<\/dt>21<\/dd> Standards<\/dt>48<\/dd> <\/dl> <\/section> Specification<\/a>Functions<\/a>State machines<\/a>Flows<\/a>Objects<\/a>Participants<\/a>Standards<\/a>Conformance<\/a>Governance<\/a>Changes<\/a>Implementers<\/a>Wire bindings<\/a>Reference scenes<\/a> <\/nav> On this page<\/p>Lineage<\/span><\/li>Profiles<\/span><\/li>Levels<\/span><\/li>Test areas<\/span><\/li>References<\/span><\/li><\/ol><\/nav>The practice this part continues.<\/h2> <\/header>2000 Common standards, many builders<\/dt>Since Argo started in 2000, its profiling floats have been built by companies and research institutions alike, all held to common standards set by an international steering team. Replaceable providers behind one shared contract is the arrangement the protocol makes normative. [1]<\/span><\/sup><\/dd> 2023 Attested identity<\/dt>The IETF RATS architecture (RFC 9334) describes how one party appraises evidence about the state of another. The protocol\u2019s Join and Admit functions apply that model to instruments: a participant begins untrusted and is admitted on evidence, not on assertion. [2]<\/span><\/sup><\/dd> <\/dl><\/section>Five conformance profiles.<\/h2>Each profile names the functions an implementation of that kind must provide.<\/p> <\/header>OBSP-NODE<\/dt>Node agents and devices: Join, Describe, Time, Observe, Qualify, Orchestrate (apply), Exit.<\/dd> OBSP-SITE<\/dt>Site controllers: OBSP-NODE plus Admit (local), Orchestrate (plan), Correct, Prove (verifier).<\/dd> OBSP-GRID<\/dt>Cluster and grid control planes: OBSP-SITE plus Federate and Exchange.<\/dd> OBSP-PROVIDER<\/dt>Hardware, software, model and data providers: Admit, Describe, Exit.<\/dd> OBSP-CONSUMER<\/dt>Applications reading products: Exchange, Correct (subscribe).<\/dd> <\/dl><\/section>Four levels, each reached on evidence.<\/h2>A level is reached only with the evidence the profile names, produced by the open conformance tool or a qualified laboratory. “Conformant” describes a tested scope only; it is never a certification.<\/p> <\/header>1 Declared<\/b>Reached only with the evidence the profile names.<\/li>2 Self-tested<\/b>Reached only with the evidence the profile names.<\/li>3 Lab-tested<\/b>Reached only with the evidence the profile names.<\/li>4 Qualified<\/b>Reached only with the evidence the profile names.<\/li>5 Suspended<\/b>A level may be suspended or withdrawn.<\/li>6 Withdrawn<\/b>A level may be suspended or withdrawn.<\/li><\/ol><\/section>What a conformance test covers.<\/h2>12 function areas and 11 state-machine areas.<\/p> <\/header>Function<\/p>Join<\/h3>8 object types, 0 roles, 5 standard references.<\/p> Function<\/p>Admit<\/h3>5 object types, 0 roles, 4 standard references.<\/p> Function<\/p>Describe<\/h3>4 object types, 0 roles, 5 standard references.<\/p> Function<\/p>Time<\/h3>3 object types, 0 roles, 4 standard references.<\/p> Function<\/p>Observe<\/h3>4 object types, 0 roles, 4 standard references.<\/p> Function<\/p>Qualify<\/h3>5 object types, 0 roles, 3 standard references.<\/p> Function<\/p>Federate<\/h3>4 object types, 0 roles, 3 standard references.<\/p> Function<\/p>Orchestrate<\/h3>6 object types, 0 roles, 5 standard references.<\/p> Function<\/p>Correct<\/h3>4 object types, 0 roles, 1 standard references.<\/p> Function<\/p>Exchange<\/h3>4 object types, 0 roles, 6 standard references.<\/p> Function<\/p>Prove<\/h3>2 object types, 0 roles, 3 standard references.<\/p> Function<\/p>Exit and decommission<\/h3>4 object types, 0 roles, 0 standard references.<\/p> State machine<\/p>Node enrolment<\/h3>10 states and 42 typed transitions.<\/p> State machine<\/p>Provider admission<\/h3>10 states and 35 typed transitions.<\/p> State machine<\/p>Data source admission<\/h3>9 states and 25 typed transitions.<\/p> State machine<\/p>Site connectivity and reconciliation<\/h3>5 states and 6 typed transitions.<\/p> State machine<\/p>Physical site lifecycle<\/h3>10 states and 9 typed transitions.<\/p> State machine<\/p>Site formation<\/h3>7 states and 6 typed transitions.<\/p> State machine<\/p>deployment plan compilation phases<\/h3>14 states and 16 typed transitions.<\/p> State machine<\/p>Reference component promotion<\/h3>7 states and 6 typed transitions.<\/p> State machine<\/p>Engineering promotion ladder<\/h3>10 states and 9 typed transitions.<\/p> State machine<\/p>Evidence and claim chain<\/h3>11 states and 10 typed transitions.<\/p> State machine<\/p>Model lifecycle<\/h3>9 states and 8 typed transitions.<\/p> <\/section>References<\/h2>Sources for the historical and standards statements on this page.<\/p> <\/header>Argo Program. “About Argo.” argo.ucsd.edu\/about\/<\/a><\/li>Birkholz, H., et al. (2023). RFC 9334, “Remote ATtestation procedureS (RATS) Architecture.” IETF. www.rfc-editor.org\/rfc\/rfc9334<\/a><\/li>Bradner, S. (1997). RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels.” IETF. www.rfc-editor.org\/rfc\/rfc2119<\/a><\/li>Leiba, B. (2017). RFC 8174, “Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words.” IETF. www.rfc-editor.org\/rfc\/rfc8174<\/a><\/li><\/ol><\/section><\/main> Read it, test it, propose a change.<\/h2>The Observatory Protocol is an open specification stewarded by the Nexus Consortium. Any party may implement it, and every change is proposed and decided in public.<\/p> Read the specification<\/a>Contribute<\/a> <\/section>
\/<\/p>Conformance<\/b> Conformance is a tested scope, stated with its evidence.<\/h1>
Five profiles define what each kind of implementation must do; four levels define how far that has been shown. A level is reached only with the evidence the profile names.<\/p> Read the specification<\/a>Contribute<\/a> Functions<\/dt>12<\/dd> State machines<\/dt>11<\/dd> Objects<\/dt>21<\/dd> Standards<\/dt>48<\/dd> <\/dl> <\/section> Specification<\/a>Functions<\/a>State machines<\/a>Flows<\/a>Objects<\/a>Participants<\/a>Standards<\/a>Conformance<\/a>Governance<\/a>Changes<\/a>Implementers<\/a>Wire bindings<\/a>Reference scenes<\/a> <\/nav> On this page<\/p>Lineage<\/span><\/li>Profiles<\/span><\/li>Levels<\/span><\/li>Test areas<\/span><\/li>References<\/span><\/li><\/ol><\/nav>The practice this part continues.<\/h2> <\/header>2000 Common standards, many builders<\/dt>Since Argo started in 2000, its profiling floats have been built by companies and research institutions alike, all held to common standards set by an international steering team. Replaceable providers behind one shared contract is the arrangement the protocol makes normative. [1]<\/span><\/sup><\/dd> 2023 Attested identity<\/dt>The IETF RATS architecture (RFC 9334) describes how one party appraises evidence about the state of another. The protocol\u2019s Join and Admit functions apply that model to instruments: a participant begins untrusted and is admitted on evidence, not on assertion. [2]<\/span><\/sup><\/dd> <\/dl><\/section>Five conformance profiles.<\/h2>Each profile names the functions an implementation of that kind must provide.<\/p> <\/header>OBSP-NODE<\/dt>Node agents and devices: Join, Describe, Time, Observe, Qualify, Orchestrate (apply), Exit.<\/dd> OBSP-SITE<\/dt>Site controllers: OBSP-NODE plus Admit (local), Orchestrate (plan), Correct, Prove (verifier).<\/dd> OBSP-GRID<\/dt>Cluster and grid control planes: OBSP-SITE plus Federate and Exchange.<\/dd> OBSP-PROVIDER<\/dt>Hardware, software, model and data providers: Admit, Describe, Exit.<\/dd> OBSP-CONSUMER<\/dt>Applications reading products: Exchange, Correct (subscribe).<\/dd> <\/dl><\/section>Four levels, each reached on evidence.<\/h2>A level is reached only with the evidence the profile names, produced by the open conformance tool or a qualified laboratory. “Conformant” describes a tested scope only; it is never a certification.<\/p> <\/header>1 Declared<\/b>Reached only with the evidence the profile names.<\/li>2 Self-tested<\/b>Reached only with the evidence the profile names.<\/li>3 Lab-tested<\/b>Reached only with the evidence the profile names.<\/li>4 Qualified<\/b>Reached only with the evidence the profile names.<\/li>5 Suspended<\/b>A level may be suspended or withdrawn.<\/li>6 Withdrawn<\/b>A level may be suspended or withdrawn.<\/li><\/ol><\/section>What a conformance test covers.<\/h2>12 function areas and 11 state-machine areas.<\/p> <\/header>Function<\/p>Join<\/h3>8 object types, 0 roles, 5 standard references.<\/p> Function<\/p>Admit<\/h3>5 object types, 0 roles, 4 standard references.<\/p> Function<\/p>Describe<\/h3>4 object types, 0 roles, 5 standard references.<\/p> Function<\/p>Time<\/h3>3 object types, 0 roles, 4 standard references.<\/p> Function<\/p>Observe<\/h3>4 object types, 0 roles, 4 standard references.<\/p> Function<\/p>Qualify<\/h3>5 object types, 0 roles, 3 standard references.<\/p> Function<\/p>Federate<\/h3>4 object types, 0 roles, 3 standard references.<\/p> Function<\/p>Orchestrate<\/h3>6 object types, 0 roles, 5 standard references.<\/p> Function<\/p>Correct<\/h3>4 object types, 0 roles, 1 standard references.<\/p> Function<\/p>Exchange<\/h3>4 object types, 0 roles, 6 standard references.<\/p> Function<\/p>Prove<\/h3>2 object types, 0 roles, 3 standard references.<\/p> Function<\/p>Exit and decommission<\/h3>4 object types, 0 roles, 0 standard references.<\/p> State machine<\/p>Node enrolment<\/h3>10 states and 42 typed transitions.<\/p> State machine<\/p>Provider admission<\/h3>10 states and 35 typed transitions.<\/p> State machine<\/p>Data source admission<\/h3>9 states and 25 typed transitions.<\/p> State machine<\/p>Site connectivity and reconciliation<\/h3>5 states and 6 typed transitions.<\/p> State machine<\/p>Physical site lifecycle<\/h3>10 states and 9 typed transitions.<\/p> State machine<\/p>Site formation<\/h3>7 states and 6 typed transitions.<\/p> State machine<\/p>deployment plan compilation phases<\/h3>14 states and 16 typed transitions.<\/p> State machine<\/p>Reference component promotion<\/h3>7 states and 6 typed transitions.<\/p> State machine<\/p>Engineering promotion ladder<\/h3>10 states and 9 typed transitions.<\/p> State machine<\/p>Evidence and claim chain<\/h3>11 states and 10 typed transitions.<\/p> State machine<\/p>Model lifecycle<\/h3>9 states and 8 typed transitions.<\/p> <\/section>References<\/h2>Sources for the historical and standards statements on this page.<\/p> <\/header>Argo Program. “About Argo.” argo.ucsd.edu\/about\/<\/a><\/li>Birkholz, H., et al. (2023). RFC 9334, “Remote ATtestation procedureS (RATS) Architecture.” IETF. www.rfc-editor.org\/rfc\/rfc9334<\/a><\/li>Bradner, S. (1997). RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels.” IETF. www.rfc-editor.org\/rfc\/rfc2119<\/a><\/li>Leiba, B. (2017). RFC 8174, “Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words.” IETF. www.rfc-editor.org\/rfc\/rfc8174<\/a><\/li><\/ol><\/section><\/main> Read it, test it, propose a change.<\/h2>The Observatory Protocol is an open specification stewarded by the Nexus Consortium. Any party may implement it, and every change is proposed and decided in public.<\/p> Read the specification<\/a>Contribute<\/a> <\/section>
On this page<\/p>
Each profile names the functions an implementation of that kind must provide.<\/p> <\/header>
A level is reached only with the evidence the profile names, produced by the open conformance tool or a qualified laboratory. “Conformant” describes a tested scope only; it is never a certification.<\/p> <\/header>
12 function areas and 11 state-machine areas.<\/p> <\/header>
Function<\/p>
8 object types, 0 roles, 5 standard references.<\/p>
5 object types, 0 roles, 4 standard references.<\/p>
4 object types, 0 roles, 5 standard references.<\/p>
3 object types, 0 roles, 4 standard references.<\/p>
4 object types, 0 roles, 4 standard references.<\/p>
5 object types, 0 roles, 3 standard references.<\/p>
4 object types, 0 roles, 3 standard references.<\/p>
6 object types, 0 roles, 5 standard references.<\/p>
4 object types, 0 roles, 1 standard references.<\/p>
4 object types, 0 roles, 6 standard references.<\/p>
2 object types, 0 roles, 3 standard references.<\/p>
4 object types, 0 roles, 0 standard references.<\/p>
State machine<\/p>
10 states and 42 typed transitions.<\/p>
10 states and 35 typed transitions.<\/p>
9 states and 25 typed transitions.<\/p>
5 states and 6 typed transitions.<\/p>
10 states and 9 typed transitions.<\/p>
7 states and 6 typed transitions.<\/p>
14 states and 16 typed transitions.<\/p>
11 states and 10 typed transitions.<\/p>
9 states and 8 typed transitions.<\/p> <\/section>References<\/h2>Sources for the historical and standards statements on this page.<\/p> <\/header>Argo Program. “About Argo.” argo.ucsd.edu\/about\/<\/a><\/li>Birkholz, H., et al. (2023). RFC 9334, “Remote ATtestation procedureS (RATS) Architecture.” IETF. www.rfc-editor.org\/rfc\/rfc9334<\/a><\/li>Bradner, S. (1997). RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels.” IETF. www.rfc-editor.org\/rfc\/rfc2119<\/a><\/li>Leiba, B. (2017). RFC 8174, “Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words.” IETF. www.rfc-editor.org\/rfc\/rfc8174<\/a><\/li><\/ol><\/section><\/main> Read it, test it, propose a change.<\/h2>The Observatory Protocol is an open specification stewarded by the Nexus Consortium. Any party may implement it, and every change is proposed and decided in public.<\/p> Read the specification<\/a>Contribute<\/a> <\/section>
Sources for the historical and standards statements on this page.<\/p> <\/header>
The Observatory Protocol is an open specification stewarded by the Nexus Consortium. Any party may implement it, and every change is proposed and decided in public.<\/p> Read the specification<\/a>Contribute<\/a> <\/section>