8Dionysus/titan-runtime-gate
skills/titan-runtime-gate/SKILL.md
--- name: titan-runtime-gate scope: project status: scaffold summary: Activate Forge mutation or Delta judgment lanes only through matching explicit runtime gates on a Titan receipt. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-runtime-gate ## Intent Use this skill when a Titan session needs to activate Forge or Delta from locked to gated state. ## Trigger boundary Use this skill when: - Fo
$ install --global
skillsauthnpx skillsauth add 8Dionysus/aoa-skills titan-runtime-gateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 11:45 AM172.7s5 files scanned
SKILL.md
- name:
- titan-runtime-gate
- scope:
- project
- status:
- scaffold
- summary:
- Activate Forge mutation or Delta judgment lanes only through matching explicit runtime gates on a Titan receipt.
- invocation_mode:
- explicit-only
titan-runtime-gate
Intent
Use this skill when a Titan session needs to activate Forge or Delta from locked to gated state.
Trigger boundary
Use this skill when:
- Forge needs a mutation gate
- Delta needs a judgment gate
- a receipt must record lane activation before proceeding
Do not use this skill when:
- Atlas, Sentinel, or Mneme are being gated unnecessarily
- Forge is requested with judgment or Delta with mutation
- the receipt does not exist
Inputs
- receipt path
- requested Titan
- gate kind
- intent text
- operator approval ref
Outputs
- updated gate state
- allowed or blocked decision
- receipt event
- lane summary
- next validation step
Procedure
- confirm receipt exists
- confirm requested Titan is Forge or Delta
- confirm gate kind matches the Titan
- record the gate event
- return the updated roster state
Contracts
- The skill is explicit-only and must not be invoked as hidden background behavior.
- Titan receipts, bridge ledgers, console state, and memory records are witnesses, not final owner truth.
- Forge mutation and Delta judgment gates must remain distinct and visible.
- Owner-repo validation and human judgment remain stronger than the local skill output.
Risks and anti-patterns
- treating Titan vocabulary as permission to widen authority
- letting receipt or replay state replace owner-repo evidence
- auto-approving Forge or Delta because a plan looks plausible
- canonizing candidate memory without source-owned confirmation
Verification
- confirm the request and outputs stayed inside the declared Titan lane
- confirm any mutation or judgment gate was explicit and recorded
- confirm source refs, receipt refs, or ledger refs are preserved when available
- confirm the result names stop lines and remaining owner validation needs
Technique traceability
Pending Titan workflow techniques:
- AOA-T-PENDING-TITAN-GATE-DISCIPLINE
- AOA-T-PENDING-TITAN-RECEIPT-LINEAGE
Adaptation points
- Replace pending technique refs with published aoa-techniques refs after the Titan workflow techniques are promoted.
- Keep repo-local command examples in owner docs or examples rather than hard-coding them into the skill law.
- If a Titan surface graduates from scaffold to reviewed, add review evidence before changing status.
Related Skills
8Dionysus/aoa-knowledge-stewardship
development
VerifiedTrustedCommunity
Sanitize private technical material into a public-safe owner-bounded derivative, or resolve authority among authored, generated, runtime, and installed sources. Use for governed incidents, logs, configs, diagnostics, or conflicting source roles. Do not use for ordinary editing, memo/session work, direct publication, or durable-memory authority.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-session-recovery
tools
VerifiedTrustedCommunity
Diagnose a reviewed recurring session/workflow failure, or carry one bounded owner repair through checkpoint, rollback, and real health verification. Use for reviewed contamination, drift, repeated route/tool failure, or an established diagnosis ready for repair. Do not use on live evidence, for vague self-improvement, or to call a proposed or merely executed change verified.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-session-harvest
tools
VerifiedTrustedCommunity
Use only when a literal ref to a closed/reviewed session packet is supplied, to extract, classify, propose promotion or branching, or identify an automation opportunity. Missing, live, or unreviewed evidence must fail closed without inventing a ref. Natural closeout preservation belongs to aoa-memo-writeback. Do not use for generic summaries, progression, direct owner writes, scheduling, mutation, or telemetry authority.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-verification
testing
VerifiedTrustedCommunity
Turn one stable technical truth into bounded evidence through contract, coverage-audit, or property mode. Use to define a named consumer seam, audit what existing checks really constrain, or express a broad invariant after manual cases establish meaning. Compose with aoa-eval when an evaluation surface must first be found or applied. Do not use for undefined behavior, generic test plans, or green checks as whole-system proof.
4SKILL.mdUpdated Jul 16, 2026