Skip to content

Commit b980bec

Browse files
author
StackMemory Bot (CLI)
committed
feat(sops): generate randomized SOPs and validation tests
Add a randomized SOP generator and 20 generated SOPs so the PROSE pipeline can be tested with more than the original 5 SOPs. - scripts/generate-random-sops.ts: generator for N randomized SOPs - docs/sops/generated/: 20 generated SOPs (IDs 1000+ to avoid collisions) - src/__tests__/sop-validation.test.ts: validates all SOP files have unique IDs, required sections, and PROSE references
1 parent a820940 commit b980bec

22 files changed

Lines changed: 770 additions & 0 deletions
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1008 Observability
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.8 Observability](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure observability is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system should detect conditions that require observability during snapshot capture.
14+
15+
2. **Action**
16+
- Upon detection, the system should retry with exponential backoff during snapshot capture.
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 observability rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to retry with exponential backoff during snapshot capture is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1104 Observability
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.4 Observability](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure observability is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system is required to detect conditions that require observability 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 observability 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: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1106 Circuit Breaking
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.6 Circuit Breaking](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure circuit breaking is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system shall detect conditions that require circuit breaking when handling external adapters.
14+
15+
2. **Action**
16+
- Upon detection, the system shall retry with exponential backoff when handling external adapters.
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 circuit breaking rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to retry with exponential backoff when handling external adapters is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1109 Authorization
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.9 Authorization](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure authorization is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system must always detect conditions that require authorization for all CLI commands.
14+
15+
2. **Action**
16+
- Upon detection, the system must always retry with exponential backoff for all CLI commands.
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 authorization rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to retry with exponential backoff for all CLI commands is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1119 Circuit Breaking
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.19 Circuit Breaking](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure circuit breaking is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system must detect conditions that require circuit breaking for cross-project operations.
14+
15+
2. **Action**
16+
- Upon detection, the system must return a structured error response for cross-project operations.
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 circuit breaking rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to return a structured error response for cross-project operations is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1211 API Versioning
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.11 API Versioning](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure api versioning is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system must always detect conditions that require api versioning for cross-project operations.
14+
15+
2. **Action**
16+
- Upon detection, the system must always log the event with context for cross-project operations.
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 api versioning rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to log the event with context for cross-project operations is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1216 Multi-Agent Coordination
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.16 Multi-Agent Coordination](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure multi-agent coordination is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system is required to detect conditions that require multi-agent coordination during ingestion.
14+
15+
2. **Action**
16+
- Upon detection, the system is required to return a structured error response during ingestion.
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 multi-agent coordination rule are observed.
25+
26+
## Non-compliance
27+
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-1218 API Versioning
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.18 API Versioning](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure api versioning is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system must always detect conditions that require api versioning for all CLI commands.
14+
15+
2. **Action**
16+
- Upon detection, the system must always log the event with context for all CLI commands.
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 api versioning rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to log the event with context for all CLI commands is considered non-compliant.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# SOP-1307 Circuit Breaking
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.7 Circuit Breaking](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure circuit breaking is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system is required to detect conditions that require circuit breaking when processing webhooks.
14+
15+
2. **Action**
16+
- Upon detection, the system is required to persist an audit record when processing webhooks.
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 circuit breaking rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to persist an audit record 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-1402 Feature Flagging
2+
3+
**Owner:** Platform Team
4+
**Status:** Active
5+
**Related PROSE Expectation:** [E.2 Feature Flagging](../specs/PROSE-platform-overview.md)
6+
7+
## Objective
8+
Ensure feature flagging is handled consistently across the platform.
9+
10+
## Procedure
11+
12+
1. **Trigger detection**
13+
- The system shall detect conditions that require feature flagging when handling external adapters.
14+
15+
2. **Action**
16+
- Upon detection, the system shall validate the digital signature when handling external adapters.
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 feature flagging rule are observed.
25+
26+
## Non-compliance
27+
28+
Failure to validate the digital signature when handling external adapters is considered non-compliant.

0 commit comments

Comments
 (0)