Skip to content

Docs/rmf crosswalk - #659

Closed
antagoninc wants to merge 8 commits into
agentrust-io:mainfrom
antagoninc:docs/rmf-crosswalk
Closed

antagoninc wants to merge 8 commits into
agentrust-io:mainfrom
antagoninc:docs/rmf-crosswalk

Conversation

@antagoninc

Copy link
Copy Markdown
Contributor

What this changes

Records Exclusion Notices under Community Specification License 1.0 Section 3 in Governance/Notices.md, as Section 9.7 provides. The applications are unpublished, so each notice identifies the parts of the Draft Specification instead of the application text. No other change.

Type of change

  • Editorial (typo, link fix, clarification: no normative effect)
  • Non-breaking spec change (new optional field, new platform profile, informative addition)
  • Breaking spec change (requires 14-day comment period and Project Lead sign-off)
  • Schema change
  • Example addition

Spec section

None changed. Governance record only.

Tests for a fix

Not a code or schema fix.

Changelog entry

None

Checklist

  • DCO sign-off on all commits (git commit -s)
  • Breaking changes marked with <!-- CHANGED: #NNN: description --> in spec text
  • Backward compatibility statement included (for breaking changes)

antagoninc and others added 8 commits October 12, 2026 15:55
…ing for v0.2 claims

Adds docs/crosswalks/nist-sp800-53-dod-ai-tailoring.md: for each Trust Record
claim, the SP 800-53 controls it is evidence for, what it establishes, what
the assessor still needs, and the Tailoring Guide item it answers. Names what
a record does not evidence for an authorization package. Nav and CHANGELOG
updated. Informative only; no normative change.

Signed-off-by: W. Alexander Ousley <antagonlabs@gmail.com>
Replace the five requested em dash cells with n/a and restore the
changelog to the PR base so the conflicting changelog hunk disappears.

Signed-off-by: Srinivasa Consultants <78673153+dinakarjs@users.noreply.github.com>
Use base SA-11 for deterministic re-performance rather than the static
analysis enhancement. Require separate evidence for cryptographic
protection and runtime application self-protection; link official NIST
page references. DoD guide references remain externally unverified.

Independent review confirmed the three-line mapping and reference scope.
This companion preserves the original crosswalk contribution.

Signed-off-by: Srinivasa Consultants <78673153+dinakarjs@users.noreply.github.com>
…aims

Retain previous mechanical and NIST corrections. Correct table/page references
and record source provenance limits without changing normative TRACE behavior.

Signed-off-by: Srinivasa Consultants <78673153+dinakarjs@users.noreply.github.com>
Signed-off-by: Srinivasa Consultants <78673153+dinakarjs@users.noreply.github.com>
Section 3.1.5 begins and states the acquisition-source and T&E evidence
on printed p. 20 of the official copy, not p. 21. Record that the table,
section and page references were re-checked against the DoD CIO host;
byte identity of the two copies is still not claimed.

Signed-off-by: W. Alexander Ousley <antagonlabs@gmail.com>
Address the three mapping corrections and five nonblocking evidence-limit observations from the current review of upstream agentrust-io#486.

Signed-off-by: Srinivasa Consultants <78673153+dinakarjs@users.noreply.github.com>
Signed-off-by: Srinivasa Consultants <78673153+dinakarjs@users.noreply.github.com>
@antagoninc
antagoninc requested review from a team, lywinged and rajnisht7 as code owners November 9, 2026 08:21
@antagoninc

Copy link
Copy Markdown
Contributor Author

Opened by mistake from an old branch. This crosswalk was merged in #486. Closing.

@antagoninc antagoninc closed this Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants