Teleportation Circle
Establish reusable deployment pipelines, standing sync routes, and repeatable migration paths.
What This Skill Does
Use this spell when you need a permanent, reliable portal between two environments — a CI/CD pipeline, a standing data sync, a repeatable deployment, or a migration path you will use more than once.
In this grimoire, Teleportation Circle is treated as a literal spell with a prototype delivery profile.
Canonical reference input: Teleportation Circle (spell).
When To Use
- You are setting up a CI/CD pipeline or deployment workflow that will be used repeatedly.
- Two systems need a standing sync route that runs reliably without manual intervention.
- A migration path needs to be codified so it can be re-run, tested, and trusted.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Define the source, destination, and what travels through the circle: code, data, configuration, or artifacts.
- Build the pipeline or sync route with explicit triggers, validation steps, and failure handling.
- Test the circle end-to-end before relying on it for production traffic.
- Document the circle's configuration, monitoring, and maintenance requirements.
- Stop for explicit confirmation before taking a live action that changes access, triggers an alert, or touches a real system boundary.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A configured, tested pipeline or sync route between source and destination.
- Documentation of triggers, validation steps, failure modes, and rollback procedures.
- A monitoring and maintenance plan — permanent portals need ongoing attention.
Pitfalls / Guardrails
- Call out the glue, permissions, or missing infrastructure before you imply this is fully operational.
- Do not create a circle and forget about it. Permanent portals need health checks, alerting, and maintenance.
- Test the circle in a non-production environment before routing real traffic through it.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the exact live target, confirmation gate, and rollback or recovery path are explicit.
- Check that any missing glue code, permissions, or future work is labeled before the skill is treated as ready.
Example Invocation
/teleportation-circle establish a reusable pipeline between these environments, with testing and monitoring built in
1---2name: teleportation-circle-23description: Use this spell when you need a permanent, reliable portal between two environments — a CI/CD pipeline, a standing data sync, a repeatable deployment, or a migration path you will use more than once.4license: CC0-1.05---6# Teleportation Circle7Establish reusable deployment pipelines, standing sync routes, and repeatable migration paths.8## What This Skill Does9Use this spell when you need a permanent, reliable portal between two environments — a CI/CD pipeline, a standing data sync, a repeatable deployment, or a migration path you will use more than once.10In this grimoire, Teleportation Circle is treated as a literal spell with a prototype delivery profile.11Canonical reference input: Teleportation Circle (spell).12## When To Use1314- You are setting up a CI/CD pipeline or deployment workflow that will be used repeatedly.15- Two systems need a standing sync route that runs reliably without manual intervention.16- A migration path needs to be codified so it can be re-run, tested, and trusted.1718## Prerequisites1920- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.2122## Procedure23241. Restate the target, the success condition, and any no-touch boundaries before taking action.252. Define the source, destination, and what travels through the circle: code, data, configuration, or artifacts.263. Build the pipeline or sync route with explicit triggers, validation steps, and failure handling.274. Test the circle end-to-end before relying on it for production traffic.285. Document the circle's configuration, monitoring, and maintenance requirements.296. Stop for explicit confirmation before taking a live action that changes access, triggers an alert, or touches a real system boundary.307. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.3132## Deliverables3334- A configured, tested pipeline or sync route between source and destination.35- Documentation of triggers, validation steps, failure modes, and rollback procedures.36- A monitoring and maintenance plan — permanent portals need ongoing attention.3738## Pitfalls / Guardrails3940- Call out the glue, permissions, or missing infrastructure before you imply this is fully operational.41- Do not create a circle and forget about it. Permanent portals need health checks, alerting, and maintenance.42- Test the circle in a non-production environment before routing real traffic through it.4344## Verification4546- Check that the result includes every deliverable promised above.47- Check that confirmed facts, assumptions, and inferences are visibly separated.48- Check that the exact live target, confirmation gate, and rollback or recovery path are explicit.49- Check that any missing glue code, permissions, or future work is labeled before the skill is treated as ready.5051## Example Invocation52```text53/teleportation-circle establish a reusable pipeline between these environments, with testing and monitoring built in54```
Hmbown