- Home
- Skills
- Workflow Automation
- 10 — Janus Ferryman · Complete Edition
Works with the AI Agents you already use
10 — Janus Ferryman · Complete Edition
Retains operation-specific reconciliation and commitment uncertainty, with practical workflows for timed-out submissions, missing confirmations and interrupted saves.
$25
10 — Janus Ferryman · Complete Edition
Example session with this skill installed
Everyday request
The form timed out after I clicked submit. I have these messages and a reference number. Help me determine what is known before I try again.
For a reproducible local example, use the included synthetic structured fixture:
{
"operation": {
"id": "upload-17",
"payload_hash": "example-payload-fingerprint"
},
"observations": [
{
"id": "receipt",
"operation_id": "upload-17",
"payload_hash": "example-payload-fingerprint",
"state": "committed",
"authoritative": true,
"final": true
},
{
"id": "unrelated",
"operation_id": "upload-16",
"payload_hash": "other",
"state": "committed",
"authoritative": true,
"final": true
}
]
}
Run the class's packaged helper on that fixture. Show the readable result, full structured output, executed Thirsty calculation and the limits of what was demonstrated.
- Read your context and instructions
- Compiled the output
Janus Ferryman — real local worked example
Example type: Actual execution of the packaged structured helper on synthetic input. This is not a claimed live customer session or a full specialist-model benchmark.
Readable work product
Supplied-record settlement status: committed
Matched observations: 1; excluded mismatches: 1
Do not retry an effect while commitment is unresolved or conflicting
This tool classifies supplied records; it does not query the provider or authenticate a receipt
Complete structured result
{
"accepted_observations": [
{
"authoritative": true,
"final": true,
"id": "receipt",
"operation_id": "upload-17",
"payload_hash": "example-payload-fingerprint",
"state": "committed"
}
],
"boundary": "This tool classifies supplied records; it does not query the provider or authenticate a receipt",
"excluded_observations": [
{
"id": "unrelated",
"reason": "Identity or payload mismatch"
}
],
"retry_advice": "Do not retry an effect while commitment is unresolved or conflicting",
"state": "committed"
}
Executed Thirsty-lang calculation
module conclave: core
drink result = 2 - 1
pour result
The helper checked the language result independently, encoded the complete structured result using the published TSCG-B codec, decoded it and compared the text. Running the standalone helper generates the result files and execution receipt. The example shown here was produced on the supplied synthetic input.
The deeper specialist use
Request: A submission timed out. One receipt refers to the original operation and another to an older operation. Work out what can be concluded without clicking submit again.
Illustrative specialist response: Bind the investigation to the original operation ID and payload fingerprint. Exclude the older operation’s receipt even if it looks successful. Separate final authoritative records, in-flight indications and unknown outcomes. If no matching final evidence exists, preserve the unresolved state and identify an authorized read-only status check. Do not retry the effect merely to learn whether the first attempt committed.
The preceding specialist response is an authored illustration, not an executed external action. The original class procedures and supporting skills remain included for an actual authorized assignment.
Next step
Replace the fixture with your own task data after checking that it fits the helper's input model, or use the conversational workflow directly with your AI host. Use a fresh output directory; the helper refuses to overwrite an existing result. Review factual classifications and missing inputs before relying on the result.
Connects securely to your tools. The creator never sees your data.
About this skill
Janus Ferryman — Complete Edition
Know whether it happened before you make it happen twice.
Retains operation-specific reconciliation and commitment uncertainty, with practical workflows for timed-out submissions, missing confirmations and interrupted saves.
One class. 47 equipped skills. The original specialist method plus six practical everyday workflows. $25 as a one-time purchase.
For uncertain submissions, lost confirmations, duplicate-risk actions, and interrupted automations. For deeper work, the class retains its original specialist equipment and source-defined method: Which outcomes remain possible, and what evidence settles the original operation?
What you actually receive
- All 40 original skills, including the specialist entrypoint, original supporting procedures, language workbench and evaluation lab.
- Six added everyday skills, listed in full below, and the new structured helper and worked example.
- 1 restored named dependency/dependencies: epistemic-status-enforcer.
- Class methods, contracts, source references, standalone task-packet tooling, executable helpers and worked examples, delivered through your connected AI.
- Standalone Thirsty-lang and TSCG-B tooling that uses the real
thirsty-lang==0.9.0runtime. Code execution requires Python 3.10+, a host execution tool and that separately installed package in the same environment. No runtime wheel is delivered through Agensi.
The specialist class: the original depth stays equipped
- Bind the investigation to the original operation ID and payload; reject mismatched receipts.
- Enumerate COMMITTED, NOT_COMMITTED, IN_FLIGHT and UNKNOWN possibilities supported by the provider contract.
- Query only authorized status/read interfaces; never invoke the commitment method to test it.
- Compare provider receipt identity, payload, time and settlement semantics.
- Use absence as decisive only when the adapter proves a complete, final lookup.
- Record the possible outcomes, eliminated alternatives, observation cut and residual uncertainty.
- Return a settled result or a bounded next observation; preserve nonce history regardless.
Specialist deliverable: settlement_record. Its source-defined result fields are operation_id, possible_outcomes, settlement, provider_observations, decisive_evidence, next_observation. These guide the work product; an actual outcome requires the task inputs, authorized tools and evidence.
Six everyday workflows — the documented practical use cases
1. Reconcile a form or upload after a timeout
Bind the exact submission, reference and payload. Check available status or confirmation records; do not treat an empty result as final without evidence of a complete lookup.
2. Match a confirmation to the action it actually confirms
Compare operation identifiers, content, target and timestamps. Exclude receipts for other actions even if the wording looks similar.
3. Decide what must be checked before retrying
List possible committed and uncommitted outcomes, identify an authorized read-only status check, and keep retries separate from investigation.
4. Find out whether a save completed
Compare the exact version or payload with a reopened view or returned receipt. Distinguish an optimistic UI message from persisted state.
5. Draft the smallest useful status inquiry
Ask the provider to identify the original operation and its final state. Include only necessary non-sensitive references supplied for that purpose; leave sending to actual authorization.
6. Keep a clear record of an uncertain outcome
Record observations, their source and finality, excluded evidence and unresolved alternatives. Preserve the original operation identity throughout.
Example 1 — what a specialist assignment can look like
You ask: A submission timed out. One receipt refers to the original operation and another to an older operation. Work out what can be concluded without clicking submit again.
Illustrative response: Bind the investigation to the original operation ID and payload fingerprint. Exclude the older operation’s receipt even if it looks successful. Separate final authoritative records, in-flight indications and unknown outcomes. If no matching final evidence exists, preserve the unresolved state and identify an authorized read-only status check. Do not retry the effect merely to learn whether the first attempt committed.
This example illustrates the class method. It is not an assertion that the proposed external investigation, model trial or system change has been executed.
Example 2 — an everyday request
The form timed out after I clicked submit. I have these messages and a reference number. Help me determine what is known before I try again.
The work product: An operation-specific status record, excluded mismatched evidence, remaining possibilities, and a safe observation to seek next.
The included local helper demonstrates a bounded part of this workflow. Its actual run on synthetic structured input produced:
Supplied-record settlement status: committed
Matched observations: 1; excluded mismatches: 1
Do not retry an effect while commitment is unresolved or conflicting
This tool classifies supplied records; it does not query the provider or authenticate a receipt
See the demo section below for its complete input, structured result and executed Thirsty calculation.
Example 3 — using the class template on your own material
Use Janus Ferryman — Complete Edition.
Goal: [the concrete result I need]
Material: [paste or attach the actual records, notes, code or facts]
Scope: [what may be inspected or changed]
Constraints: [time window, dependencies, formats and important conditions]
Deliver: An operation-specific status record, excluded mismatched evidence, remaining possibilities, and a safe observation to seek next.
Use the original specialist method when the problem requires it.
Ask only for missing facts that materially change the result.
Show what you actually did and what still needs a decision.
For a simple request, use only the relevant everyday mode. For advanced work, select the original specialist procedures. Keeping the equipment available does not require loading every skill into every interaction.
Every skill available in this pack (47 total)
-
architecture-decision-recorder — Edition XXII source-attributed supplemental agent procedure: Architecture choice and tradeoff recording.
-
build-reproducibility-receipts — Create verifiable local build and test receipts linking source snapshots, commands and exact artifact bytes.
-
ceta-authority-timeline-autopsy — Reconstruct possible CETA event and authority histories across occurrence, recording, observation, and validity time, and identify distinguishing evidence.
-
ceta-class-router — Choose a Thirstforged Conclave sub-agent class for a CETA task, prepare its bounded assignment and exact skill inventory, and distinguish instruction packets from native profile activation.
-
ceta-evidence-cross-examination — Cross-examine a Thirstforged Conclave result against raw observations, exact source bindings, expected predicates, and actual reviewer identity before integration.
-
ceta-frame-authority-confusion — Build bounded TSCG/TSCG-B and policy specimens that separate valid framing and checksums from legitimate actor, scope, freshness, and execution authority.
-
ceta-incentive-failure-societies — Run bounded deterministic agent-society simulations that expose incentive conflicts, metric gaming, missing stakeholders, and collective failure despite local compliance.
-
ceta-interrupted-effect-reconstruction — Reconstruct interrupted or cancelled effects from receipts and effect-owner observations, preserving unknown outcomes and preventing unexamined retries.
-
ceta-rare-failure-cultivation — Search reproducible crash, cancellation, delay, ordering, and partial-progress schedules in disposable fixtures to expose rare CETA failures.
-
ceta-utf-contract-map — Map a CETA task to the six Universal Thirsty Family tiers and exact isolated Thirsty-Lang 0.9.0 tools, preserving the difference between analysis, integrity, and authority.
-
codex-api-contract-auditor — Use for inspect api definition documents, json contracts and documentation consistency.
-
codex-authority-resolver — Use for resolve governing clause identity and applicable authorization without assuming precedence.
-
codex-autonomy-review — Use for evaluate competence evidence and legitimate authority for autonomy changes.
-
codex-build-reproducer — Use for inventory local build ingredients and reproducibility conditions.
-
codex-claim-integrity — Use for prevent observed/inferred/proposed/implemented states from being conflated.
-
codex-evidence-ledger — Use for validate referenced evidence paths and source identity.
-
codex-failure-reproducer — Use for create reproducibility inputs from logs and source; do not invent successful runs.
-
codex-hostile-review — Use for challenge the implementation for bypass, risk, and missing negative evidence.
-
codex-identity-verifier — Use for review verified identity boundary instead of treating familiarity as authentication.
-
codex-integration-test-auditor — Use for inspect integration test entrypoints and source dependencies.
-
codex-owner-decision — Use for prepare and verify actual owner decisions, never invent approval.
-
codex-recovery-rollback — Use for assess rollback artifacts, durable continuity and recovery prerequisites.
-
codex-repo-preservation — Use for protect untracked work, check provenance and refuse destructive cleanup.
-
codex-retirement-check — Use for verify decommission/retirement plans for evidence and retained obligations.
-
codex-runtime-architecture — Use for inspect declared runtime entrypoints, interlocks and operational boundaries.
-
codex-runtime-health — Use for inspect health-related logs and configs as static evidence, not live monitoring.
-
codex-scope-guardian — Use for prevent invented or silently widened objectives and repository scope.
-
codex-source-integrity — Use for check bundled source document checksums and protect observed provenance.
-
conclave-evaluation-lab — Design held-out comparisons of the equipped agent and baseline workflows with matched models, tools, budgets, and recorded evidence.
-
conclave-janus-ferryman — Retains operation-specific reconciliation and commitment uncertainty, with practical workflows for timed-out submissions, missing confirmations and interrupted saves.
-
conclave-language-workbench — Use Thirsty-lang as the primary local language and TSCG-B to encode/decode exact UTF-8 task and result text.
-
epistemic-status-enforcer — Apply explicit epistemic status to meaningful claims.
-
identity-continuity-auditor — Edition XXII source-attributed supplemental agent procedure: Continuity and principal identity auditing.
-
janus-ferryman-confirmation-match — Match a confirmation to the action it actually confirms.
-
janus-ferryman-duplicate-risk — Decide what must be checked before retrying.
-
janus-ferryman-interrupted-save — Find out whether a save completed.
-
janus-ferryman-settlement-record — Keep a clear record of an uncertain outcome.
-
janus-ferryman-status-followup — Draft the smallest useful status inquiry.
-
janus-ferryman-submission-timeout — Reconcile a form or upload after a timeout.
-
memory-governance-designer — Edition XXII source-attributed supplemental agent procedure: Provenance-first memory rules.
-
polyglot-stack-selector — Select practical combinations of programming languages and runtime boundaries for one application.
-
proof-obligation-generator — Edition XXII source-attributed supplemental agent procedure: Execution proof obligation construction.
-
property-fuzz-test-engineer — Implement executable property-based tests, deterministic fuzz harnesses and failure minimization for source code.
-
python-production-coder — Implement and repair working Python applications, libraries and asynchronous services.
-
state-machine-coder — Implement real finite-state systems, workflows and lifecycle logic with explicit transition guards, invariants and recovery.
-
thirsty-work-orchestrator — Edition XXII source-attributed supplemental agent procedure: Role graph scheduling and evidence handoff.
-
type-contract-architect — Create implementable domain types and API contracts before coding.
Thirsty-lang and TSCG-B in practice
Run the packaged helper with Python 3.10+ to generate a readable result, structured JSON, the executed .thirsty calculation, a binary .tscg-b result and an execution receipt. The helper executes supported arithmetic in Thirsty-lang and independently checks the result; Python handles structured input and the domain algorithm. TSCG-B preserves result text through binary encode/decode. A valid frame does not itself prove the text is true or authorize an action.
Preservation and validation
Every original skill identity and the specialist methods remain, together with the six everyday additions and repaired named dependencies. The Agensi upload layout adapts executable scripts and reference delivery; historical source files and preservation records remain in the creator's original archive.
The repaired collection passed 409 local delivery and execution checks, including all 19 standalone class helpers, real Thirsty-lang calculations, TSCG-B round trips, exact task packets, delivery limits and negative cases. Independent checks also passed all 52 distinct audit-tool bindings and their source-index lookups. Six compiler-specific examples were not executed because their compiler dependencies were absent. These results do not establish every AI host's behavior, marketplace approval, live buyer retrieval, frontier-model superiority or revenue.
Start using it
Connect your AI to Agensi and ask: “Use my Agensi skill 10 — Janus Ferryman · Complete Edition. My goal is [result]. Here is my actual material: [notes, records or code].” The pack provides an index; your AI loads the class entrypoint skills/conclave-janus-ferryman/SKILL.md, then loads the supporting skills relevant to your task. Purchasing the pack does not automatically run all its skills at once.
Text and reasoning workflows run through your existing AI. Standalone scripts additionally require Python 3.10+ and a code execution tool. Thirsty-lang and TSCG-B execution requires thirsty-lang==0.9.0 installed separately in that environment; your AI should explain missing requirements before starting. Scripts are fetched unchanged through Agensi, executed temporarily and removed. Task result files can be delivered to you; the purchased skill is not installed as a downloadable local folder.
Image, video, voice and data services from Agensi's optional tools catalog are separate paid services. This pack does not require adding those services merely to use its text workflows or Python helpers. External actions, compiler tasks and account access still require the actual relevant host tools and your permission.
This is a skill/class package for an existing compatible AI host. It does not supply model weights, hosted compute, API credits, automatic account connections or permissions. The included helpers accept bounded structured inputs; they are not general document parsers or substitutes for semantic review. Their actual synthetic-fixture outputs are distinguished from authored specialist illustrations. Local preservation/tool checks do not establish correctness on arbitrary tasks, frontier-model superiority, customer results or revenue. Optional UTF analysis features may require additional dependencies. Marketplace ingestion of the final multi-skill ZIP remains subject to the receiving platform’s actual review.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Requires
Permissions
Read Files, Write Files and Terminal/Shell support the optional local examples and authorized project work. Work stays within the user-approved scope. Browser, network, services and credentials are task-dependent and are not granted by this package. A draft, recommendation or prepared payload is not evidence of an external action.