Skip to content

Commit 4f0e203

Browse files
author
StackMemory Bot (CLI)
committed
chore(sops): rotate generated SOPs — replace randomized set with new batch
1 parent 6b7a6ee commit 4f0e203

40 files changed

Lines changed: 607 additions & 533 deletions
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1001 Rate Limiting
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.13 Rate Limiting](../specs/PROSE-platform-overview.md#e13-rate-limiting)
6+
7+
## Objective
8+
Ensure rate limiting is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system is required to detect conditions that require rate limiting for cross-project operations.
14+
15+
2. **Action**
16+
- Upon detection, the system is required to persist an audit record for cross-project operations.
17+
18+
3. **Verification**
19+
- Each occurrence is required to be traceable to a decision node or audit log entry.
20+
21+
## Verification
22+
23+
- Run the relevant integration test suite.
24+
- Expected result: no violations of the rate limiting rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to persist an audit record for cross-project operations is considered non-compliant.
Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
1-
# SOP-1104 Observability
1+
# SOP-1002 Observability
22

33
**Owner:** Platform Team
44
**Status:** Active
5-
**Related PROSE Expectation:** [E.4 Observability](../specs/PROSE-platform-overview.md)
5+
**Related PROSE Expectation:** [E.7 Observability](../specs/PROSE-platform-overview.md#e7-observability)
66

77
## Objective
88
Ensure observability is handled consistently across the platform.
99

1010
## Procedure
1111

1212
1. **Trigger detection**
13-
- The system is required to detect conditions that require observability for cross-project operations.
13+
- The system is required to detect conditions that require observability during ingestion.
1414

1515
2. **Action**
16-
- Upon detection, the system is required to persist an audit record for cross-project operations.
16+
- Upon detection, the system is required to return a structured error response during ingestion.
1717

1818
3. **Verification**
1919
- Each occurrence is required to be traceable to a decision node or audit log entry.
@@ -25,4 +25,4 @@ Ensure observability is handled consistently across the platform.
2525

2626
## Non-compliance
2727

28-
Failure to persist an audit record for cross-project operations is considered non-compliant.
28+
Failure to return a structured error response during ingestion is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1003 API Versioning
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.18 API Versioning](../specs/PROSE-platform-overview.md#e18-api-versioning)
6+
7+
## Objective
8+
Ensure api versioning is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system should detect conditions that require api versioning for every API endpoint.
14+
15+
2. **Action**
16+
- Upon detection, the system should enforce the configured rate limit for every API endpoint.
17+
18+
3. **Verification**
19+
- Each occurrence should be traceable to a decision node or audit log entry.
20+
21+
## Verification
22+
23+
- Run the relevant integration test suite.
24+
- Expected result: no violations of the api versioning rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to enforce the configured rate limit for every API endpoint is considered non-compliant.

docs/sops/generated/sop-1615-secret-rotation.md renamed to docs/sops/generated/sop-1004-dependency-management.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
# SOP-1615 Dependency Management
1+
# SOP-1004 Dependency Management
22

33
**Owner:** Platform Team
44
**Status:** Active
5-
**Related PROSE Expectation:** [E.15 Dependency Management](../specs/PROSE-platform-overview.md)
5+
**Related PROSE Expectation:** [E.15 Dependency Management](../specs/PROSE-platform-overview.md#e15-dependency-management)
66

77
## Objective
88
Ensure dependency management is handled consistently across the platform.
@@ -13,7 +13,7 @@ Ensure dependency management is handled consistently across the platform.
1313
- The system is required to detect conditions that require dependency management when querying the graph.
1414

1515
2. **Action**
16-
- Upon detection, the system is required to expire cached entries on update when querying the graph.
16+
- Upon detection, the system is required to persist an audit record when querying the graph.
1717

1818
3. **Verification**
1919
- Each occurrence is required to be traceable to a decision node or audit log entry.
@@ -25,4 +25,4 @@ Ensure dependency management is handled consistently across the platform.
2525

2626
## Non-compliance
2727

28-
Failure to expire cached entries on update when querying the graph is considered non-compliant.
28+
Failure to persist an audit record when querying the graph is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1005 Retry Policy
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.23 Retry Policy](../specs/PROSE-platform-overview.md#e23-retry-policy)
6+
7+
## Objective
8+
Ensure retry policy is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system must always detect conditions that require retry policy when processing webhooks.
14+
15+
2. **Action**
16+
- Upon detection, the system must always isolate failures to the affected scope when processing webhooks.
17+
18+
3. **Verification**
19+
- Each occurrence must always be traceable to a decision node or audit log entry.
20+
21+
## Verification
22+
23+
- Run the relevant integration test suite.
24+
- Expected result: no violations of the retry policy rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to isolate failures to the affected scope when processing webhooks is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1006 Observability
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.7 Observability](../specs/PROSE-platform-overview.md#e7-observability)
6+
7+
## Objective
8+
Ensure observability is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system must always detect conditions that require observability when querying the graph.
14+
15+
2. **Action**
16+
- Upon detection, the system must always validate the digital signature when querying the graph.
17+
18+
3. **Verification**
19+
- Each occurrence must always be traceable to a decision node or audit log entry.
20+
21+
## Verification
22+
23+
- Run the relevant integration test suite.
24+
- Expected result: no violations of the observability rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to validate the digital signature when querying the graph is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1007 Observability
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.7 Observability](../specs/PROSE-platform-overview.md#e7-observability)
6+
7+
## Objective
8+
Ensure observability is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system shall detect conditions that require observability when querying the graph.
14+
15+
2. **Action**
16+
- Upon detection, the system shall enforce the configured rate limit when querying the graph.
17+
18+
3. **Verification**
19+
- Each occurrence shall be traceable to a decision node or audit log entry.
20+
21+
## Verification
22+
23+
- Run the relevant integration test suite.
24+
- Expected result: no violations of the observability rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to enforce the configured rate limit when querying the graph is considered non-compliant.

docs/sops/generated/sop-1008-feature-flagging.md

Lines changed: 0 additions & 28 deletions
This file was deleted.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1008 Secret Rotation
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.16 Secret Rotation](../specs/PROSE-platform-overview.md#e16-secret-rotation)
6+
7+
## Objective
8+
Ensure secret rotation is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system must always detect conditions that require secret rotation for every API endpoint.
14+
15+
2. **Action**
16+
- Upon detection, the system must always expire cached entries on update for every API endpoint.
17+
18+
3. **Verification**
19+
- Each occurrence must always be traceable to a decision node or audit log entry.
20+
21+
## Verification
22+
23+
- Run the relevant integration test suite.
24+
- Expected result: no violations of the secret rotation rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to expire cached entries on update for every API endpoint is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1009 Observability
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.7 Observability](../specs/PROSE-platform-overview.md#e7-observability)
6+
7+
## Objective
8+
Ensure observability is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system must detect conditions that require observability for every API endpoint.
14+
15+
2. **Action**
16+
- Upon detection, the system must expire cached entries on update for every API endpoint.
17+
18+
3. **Verification**
19+
- Each occurrence must be traceable to a decision node or audit log entry.
20+
21+
## Verification
22+
23+
- Run the relevant integration test suite.
24+
- Expected result: no violations of the observability rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to expire cached entries on update for every API endpoint is considered non-compliant.

0 commit comments

Comments
 (0)