Allura Approve Promotion

Approve pending proposals for promotion into the semantic memory store.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill allura-approve-promotion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Allura Approve Promotion
Source: https://github.com/Charitablebusinessronin/Allura_Memory/tree/main/.claude/skills/allura-approve-promotion
Command: npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill allura-approve-promotion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Curators need a controlled, auditable mechanism to promote only vetted proposals from pending status into the semantic memory store, ensuring governance and traceability.

Core Features & Use Cases

  • HITL-based promotion: approve proposals and promote them to Neo4j after review.
  • Auditability: returns a memory_id and witness_hash for traceability, with group_id and curator_id recorded.
  • Guardrails: enforces pending status, non-system curator identities, and optional rationale in SOC2 mode.

Quick Start

Approve a pending proposal by providing group_id, proposal_id, curator_id, and an optional rationale.

Frequently Asked Questions about Allura Approve Promotion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I approve a pending proposal for promotion into a semantic memory store?

To approve a pending proposal for promotion into the semantic memory store, you provide group_id, proposal_id, curator_id, and an optional rationale to validate the proposal through human-in-the-loop review.

What audit records are generated when promoting memory proposals to Neo4j?

Promoting memory proposals to Neo4j generates a memory_id and witness_hash for audit traceability, while recording the group_id and curator_id to ensure governance compliance.

Does SOC2 rationale compliance require specific inputs for memory curation approval?

SOC2 rationale compliance requires an optional rationale input during memory curation approval, enforcing pending status checks and non-system curator identities under the allura-* namespace.

What are the prerequisites for human-in-the-loop validation of semantic memory promotion?

Human-in-the-loop validation of semantic memory promotion requires group_id, proposal_id, curator_id, and optional rationale, enforcing that the proposal is in pending status and the curator is a non-system identity.

Why would a memory promotion approval fail governance checks?

A memory promotion approval fails governance checks if the proposal is not in pending status, the curator identity is a system account, or required inputs like group_id and proposal_id are missing.

What is HITL validation for semantic memory curation?

HITL validation for semantic memory curation is a controlled governance mechanism where human curators review and approve pending proposals before they are promoted into the Neo4j semantic memory store.