API: Governed memory promotion — write gates for experiential memory

> **Roadmap:** Review feedback quorum; Trust-aware retrieval; Write-ahead validation
> **Priority:** P3

## Component

API or orchestration

## Describe the feature

Add configurable **write gates** before AgentCore Memory writes so experiential/episodic content is promoted only when quality criteria are met. Ungoverned cross-task memory amplifies noise and error propagation (arXiv:2605.18747 §3.2.3–3.2.4, MemGovern).

ABCA memory is fail-open today — correct for availability, but production profiles need governed retention.

## Use case

- **Regulated teams** require human-validated or merge-corroborated memory before reuse.
- **Review feedback loop** promotes rules only after quorum (roadmap) — this issue provides the generic gate mechanism.
- **Operators** tune `workshop` (permissive) vs `team-default` (governed) policy profiles (V2).

## Proposed solution

1. Blueprint field: `memory_promotion_policy`:

```yaml
memory_promotion_policy:
mode: permissive | governed
rules:
- insight_type: agent_self_feedback
require: task_status_completed
- insight_type: review_rule
require: quorum_met # defers to review feedback quorum issue
```

2. Orchestrator/agent checks policy before memory write; rejected writes log `memory_write_rejected` TaskEvent with reason.

3. Default: `permissive` (current behavior).

4. Document policy packs in Cedar/HITL docs cross-link.

### Acceptance criteria

- [ ] Policy schema on Blueprint / RepoConfig
- [ ] Gate enforced on memory write path; fail-open on gate evaluation errors (memory safety preserved)
- [ ] Rejection events in TaskEvents
- [ ] `team-default` example policy in docs (not necessarily deployed default)
- [ ] Tests for allow/deny paths

## Other information

- **Extends:** Review feedback quorum, Trust-aware retrieval, Write-ahead validation (roadmap)
- **Paper:** arXiv:2605.18747 MemGovern, experiential memory governance
- **Existing:** AgentCore Memory fail-open (shipped)

## Acknowledgements

- [ ] I may be able to implement this feature
- [ ] This might be a breaking change

Start by locating the Blueprint/RepoConfig schema and the existing AgentCore Memory write path. Trace how TaskEvents are emitted, then review the Cedar/HITL documentation references. Done means configurable permissive and governed policies, allow/deny tests, fail-open evaluation errors, rejection events, and a documented team-default example.

Written by the indexing model from the issue text.