Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion standard/5_Auditability/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -820,7 +820,7 @@ When the platform depends on external AI/ML models (for example, third-party LLM
8. If baseline test results deviate beyond a defined tolerance on any safety-critical decision, the platform MUST alert the operator and MUST NOT proceed with affected decision paths until the drift is reviewed and acknowledged.
9. Drift detection results MUST be logged and available to customers.

> **See also:** APTS-TP-002 (model version pinning), APTS-TP-019 (model provenance and training data governance), APTS-TP-022 (re-attestation on material model change), APTS-AR-017 (regression testing triggered by model updates), APTS-AR-018 (customer notification for behavior-affecting model updates).
> **See also:** APTS-TP-002 (model version pinning), APTS-TP-019 (model provenance and training data governance), APTS-TP-022 (re-attestation on material model change), APTS-AR-017 (regression testing triggered by model updates), APTS-AR-018 (customer notification for behavior-affecting model updates). For an illustrative evidence format, see the [Model Change and Drift Record Template](../appendix/Model_Change_and_Drift_Record_Template.md).

### Verification

Expand Down
6 changes: 3 additions & 3 deletions standard/7_Supply_Chain_Trust/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ Organizations MUST implement version pinning for all AI models to enable change
- Find rollback procedure documentation
- Verify testing before production deployment

> **See also:** APTS-AR-019 (AI/ML model change tracking and drift detection), APTS-TP-019 (AI model provenance and training data governance)
> **See also:** APTS-AR-019 (AI/ML model change tracking and drift detection), APTS-TP-019 (AI model provenance and training data governance). For an illustrative evidence format, see the [Model Change and Drift Record Template](../appendix/Model_Change_and_Drift_Record_Template.md).

---

Expand Down Expand Up @@ -409,7 +409,7 @@ Organizations MUST establish and document a data retention policy that specifies
- Verify deletion method is documented and appropriate to the storage medium
- Check audit logs: verify deletion events are recorded with timestamp and method

> **See also:** APTS-TP-016 (data destruction proof and certification)
> **See also:** APTS-TP-016 (data destruction proof and certification). For an illustrative evidence format, see the [Data Retention and Disposal Record Template](../appendix/Data_Retention_and_Disposal_Record_Template.md).

---

Expand Down Expand Up @@ -623,7 +623,7 @@ Foundation model changes are not routine dependency updates. A model upgrade can
4. **Customer notification review:** Verify that customers with active engagements at the time of the change were notified within the timeframe stated in the operator's policy, and that the notification included the outcome of the re-assessment.
5. **Rollback test:** Verify that the prior model configuration and disclosure are preserved and that the operator's runbook supports reverting to the prior configuration under APTS-TP-002.

> **See also:** APTS-TP-001 (provider vetting), APTS-TP-002 (model version pinning and change management), APTS-TP-021 (foundation model disclosure and capability baseline), APTS-AR-019 (continuous model change tracking and drift detection).
> **See also:** APTS-TP-001 (provider vetting), APTS-TP-002 (model version pinning and change management), APTS-TP-021 (foundation model disclosure and capability baseline), APTS-AR-019 (continuous model change tracking and drift detection). For an illustrative evidence format, see the [Model Change and Drift Record Template](../appendix/Model_Change_and_Drift_Record_Template.md).

---

Expand Down
2 changes: 2 additions & 0 deletions standard/Getting_Started.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,8 @@ Depending on your role:
| [Scope Change Decision Record Template](appendix/Scope_Change_Decision_Record_Template.md) | Informative | Template for documenting approved, rejected, constrained, or deferred scope changes during an engagement |
| [Autonomy Downgrade Matrix Template](appendix/Autonomy_Downgrade_Matrix_Template.md) | Informative | Template for documenting downgrade triggers, autonomy caps, re-authorization paths, and evidence preservation |
| [Threshold Configuration Template](appendix/Threshold_Configuration_Template.md) | Informative | Simple starter table for documenting operational thresholds, escalation points, and stop conditions |
| [Model Change and Drift Record Template](appendix/Model_Change_and_Drift_Record_Template.md) | Informative | Template for documenting model changes, behavioral comparisons, drift detections, re-attestation decisions, and rollback evidence |
| [Data Retention and Disposal Record Template](appendix/Data_Retention_and_Disposal_Record_Template.md) | Informative | Template for documenting retention decisions, secure deletion, disposal verification, exceptions, and customer deletion requests |
| [Advisory Requirements](appendix/Advisory_Requirements.md) | Informative | Best-practice requirements not gated to any compliance tier |

## Common Questions
Expand Down
2 changes: 2 additions & 0 deletions standard/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,8 @@ The [appendices](./appendix/) provide cross-cutting resources: checklists, compl
| [Scope Change Decision Record Template](./appendix/Scope_Change_Decision_Record_Template.md) | Informative template for documenting approved, rejected, constrained, or deferred scope changes during an engagement |
| [Autonomy Downgrade Matrix Template](./appendix/Autonomy_Downgrade_Matrix_Template.md) | Informative template for documenting downgrade triggers, autonomy caps, re-authorization paths, and evidence preservation |
| [Threshold Configuration Template](./appendix/Threshold_Configuration_Template.md) | Simple starter table for documenting operational thresholds, escalation points, and stop conditions |
| [Model Change and Drift Record Template](./appendix/Model_Change_and_Drift_Record_Template.md) | Informative template for documenting model changes, behavioral comparison, drift review, re-attestation, and rollback evidence |
| [Data Retention and Disposal Record Template](./appendix/Data_Retention_and_Disposal_Record_Template.md) | Informative template for documenting retention decisions, disposal execution, deletion verification, exceptions, and customer deletion requests |
| [Evidence Package Manifest](./appendix/Evidence_Package_Manifest.md) | Illustrative manifest for finding evidence, provenance, and downstream handoff |
| [Evidence Package Manifest Example](./appendix/examples/Evidence_Package_Manifest_Example.md) | Fictional completed example showing finding evidence, provenance, redaction, and export handoff |
| [Conformance Claim Schema](./appendix/Conformance_Claim_Schema.md) | Illustrative machine-readable schema for structured conformance claims |
Expand Down
Loading
Loading