"By repurposing the construction industry's KYK (Hazard Prediction Activity) framework, I built a decision-support tool for complex systems during confusing periods. I believe it will be genuinely useful. Please lend a hand in maintaining it."
When a complex system enters a confusing period—such as immediately after a multi-stack vulnerability disclosure, a certificate/supply-chain disruption, or an infrastructure incident—senior engineers and incident leads do not need an AI that sounds overconfident. They need a structured way to separate what is verified in primary sources, what remains unknown (UNKNOWN), which steps must be held (HOLD), and which dependencies to inspect next, so a responsible human can decide and hand off the state without losing the evidence.
Try the five-step screening directly in your browser: distinguish unknown conditions from stop boundaries, identify three critical risks and prepare a handoff.
YamRail is developing an operational and execution foundation that keeps AI proposals (Evidence / Hypothesis) strictly separate from human judgment and authority (Judgment / Authority), so successors can reconstruct work state and open conditions even when personnel or AI models change. Explore our live catalog and beta tools, and help us maintain and improve this foundation.
Rooted in Japanese construction sites, Kiken Yochi Katsudo (KYK / Hazard Prediction Activity) is not top-down micromanagement. It is a practitioner-driven decision framework where frontline workers actively identify hazards under uncertain conditions, narrow down critical risks into actionable commitments, and human foremen/leads lock in safety boundaries (HOLD) and take final accountability. YamRail brings this frontline-first structure to complex systems across software, infrastructure, power, and hybrid engineering.
| Construction-Site KYK Step | Decision Support for Complex Systems in Confusing Periods |
|---|---|
| 1. Verify Site & Work Conditions | Record system architecture, dependencies, versions, and primary advisories while keeping occurrence, detection, and publication dates distinct. |
| 2. Extract Top 3 Hazard Scenarios | Separate raw search hits from primary evidence and structure up to 3 critical impact scenarios with their preconditions. |
| 3. Isolate UNKNOWN & HOLD Boundaries | Never close missing facts by guessing; isolate affected edges as UNKNOWN / HOLD while healthy independent work continues (LOCAL_HOLD != GLOBAL_STOP). |
| 4. Optional Read-Only Configuration Screening | When requested, compare real configurations or repositories in read-only mode to list open questions (no autonomous edits or execution). |
| 5. Practitioner Action Alignment, Lead Boundary Lock & Handoff | Frontline engineers align on countermeasures and stop conditions while human leads assume final adoption accountability, handing off primary sources, dependency graphs, and revision histories to reduce redundant re-investigations. Rework and cost reductions remain unmeasured value hypotheses. |
Help keep this tool useful beyond a one-off prototype. Your support is intended to sustain these seven practical areas of ongoing work.
Because we are asking for operational fuel, YamRail is engineered with the design goal of minimizing wasted compute and redundant API calls. However, efficiency measures do not make infrastructure free—operating, auditing, and maintaining the system still requires paid infrastructure and human upkeep.
Routine public chat and KYK beta requests route exclusively to lightweight LUNA (gpt-5.6-luna); runtime invocation of heavier models is prohibited (0 calls).
YamRail Core separates a lightweight specification for routine prompt loading while keeping the full specification as an on-demand reference specification.
Aims to run schema, revision, and input-boundary checks on CPU before reserving budget or calling paid LLM APIs.
Combines output-token caps (512 tokens in CF), minimum-closure explanation control , and the operating rule capping routine live acceptance at 3 primary runs.
Modeled on civil-engineering partial acceptance , post-acceptance changes trigger an impact walk that reopens only affected dependency edges rather than re-running all tests.
A design target to reuse saved evidence, receipts, and hash-bound source records across subsequent steps to avoid repeated retrieval or re-investigation .
Shares the Firestore integer budget-reservation tool and common model-profile adapter across workfaces to avoid duplicate code and redundant live probes.
Under the Safe-Stop Doctrine and external checkpoint ledger, affected work stops safely at a LOCAL_HOLD and reconstructs state in a fresh process.
UNKNOWN. Final provider and cloud billing invoices are unreconciled, and UNKNOWN != ZERO.Seven tiers accept one-time USD support through PayPal. See each tier for deliverables, per-buyer scope and delivery timing. Payment and fulfillment are tracked separately. $2,500+ requires an individual quote.
FUEL-10PayPal Live / USD — scope of delivery below
A candidate edited edition connecting actual findings, counterevidence and repairs to source records; not a sale of free originals.
CASEBOOK_01.mdCASEBOOK_01.pdfCASEBOOK_SOURCE_INDEX.csvOne-time static delivery (proposed 10 business days) applicable only after human approval of rights, contract and capacity. No recurring service period or async Q&A.
Public access is separate from redistribution permission. Free originals remain free; paid value is editing, crosswalks and reproducible instructions. Private originals, third-party works without permission and personal data are excluded.
The deliverables, SLA and rights boundary stated for this tier apply. Fulfillment is tracked separately after payment.
[Tier exclusions] No CLI execution rights, user-host runtime guarantee, external API quota or private repository permissions.
FUEL-25PayPal Live / USD — scope of delivery below
Adds an A3-equivalent edited diagram and crosswalk tracing sources, findings, repairs and retests to FUEL-10.
FUEL10_EDITIONREVIEW_FLOW.svg + REVIEW_FLOW.pdfFINDING_SOURCE_CROSSWALK.csvOne-time static delivery of the edition, A3 diagram and crosswalk (proposed 15 business days) after human approval of rights, contract and capacity. No recurring service period.
Public access is separate from redistribution permission. Free originals remain free; paid value is editing, crosswalks and reproducible instructions. Private originals, third-party works without permission and personal data are excluded.
The deliverables, SLA and rights boundary stated for this tier apply. Fulfillment is tracked separately after payment.
[Tier exclusions] No CLI execution rights, user-host runtime guarantee, external API quota or private repository permissions.
FIELD_MANUALPayPal Live / USD — scope of delivery below
Four proposed chapters link adversarial review, revision and SHA256, counterexample tests, and stop/handoff to existing tools.
FIELD_MANUAL.md + .pdfINSPECTION_CHECKLIST.csvSOURCE_AND_LIMITS.csvOne-time delivery of the 4-chapter manual and two CSV registers (proposed 20 business days) after human approval of rights, contract and capacity. Excludes runtime or Q&A.
Public access is separate from redistribution permission. Free originals remain free; paid value is editing, crosswalks and reproducible instructions. Private originals, third-party works without permission and personal data are excluded.
The deliverables, SLA and rights boundary stated for this tier apply. Fulfillment is tracked separately after payment.
[Tier exclusions] No CLI execution rights, user-host runtime guarantee, external API quota or private repository permissions.
BUILDER_KITPayPal Live / USD — scope of delivery below
A proposed kit selects synthetic examples from existing tile, CPU/GPU and revision fixtures after rights clearance, with edited reproduction instructions.
QUALIFIED_FIXTURES.jsonRUN_LOCAL.py + ENVIRONMENT_LOCK.jsonEXPECTED_RESULTS.json + REUSE_GUIDE.mdOne-time delivery of the synthetic fixture kit and local runner (proposed 30 business days) after rights clearance and human approval. Excludes CLI agent execution rights or ongoing support.
Public access is separate from redistribution permission. Free originals remain free; paid value is editing, crosswalks and reproducible instructions. Private originals, third-party works without permission and personal data are excluded.
The deliverables, SLA and rights boundary stated for this tier apply. Fulfillment is tracked separately after payment.
[Tier exclusions] No CLI execution rights, user-host runtime guarantee, external API quota or private repository permissions.
WORKBENCH_PASSPayPal Live / USD — scope of delivery below
The baseline is a completed synthetic workface specimen: order, dependencies, counterexamples, inspection and recovery, plus one correction diff within 90 days after delivery. No runtime access.
SYNTHETIC_ORDER.yaml + DEPENDENCIES.jsonACCEPTANCE_AND_RESTORE.md + FIXTURES.jsonHANDOFF_RECORD.md + CORRECTION_DIFF.patchProposed terms after human approval: 30 business days for initial specimen delivery, plus one bounded specimen correction diff within 90 days (10-business-day async response). No custom build or runtime.
Public access is separate from redistribution permission. Free originals remain free; paid value is editing, crosswalks and reproducible instructions. Private originals, third-party works without permission and personal data are excluded.
The deliverables, SLA and rights boundary stated for this tier apply. Fulfillment is tracked separately after payment.
[Tier exclusions] No CLI execution rights, user-host runtime guarantee, external API quota or private repository permissions.
FOREMAN_LABPayPal Live / USD — scope of delivery below
Four research-note editions and intake with recorded eligibility reasons for up to three counterexample proposals over 12 months. No guaranteed benchmark participation, adoption or repair.
RESEARCH_NOTESCOUNTEREXAMPLE_INTAKEINTAKE_STATUS.csvInitial delivery target: 30 business days; 4 research notes over 365 days; async disposition for up to 3 counterexamples within a target of 10 business days.
Public access is separate from redistribution permission. Free originals remain free; paid value is editing, crosswalks and reproducible instructions. Private originals, third-party works without permission and personal data are excluded.
The deliverables, SLA and rights boundary stated for this tier apply. Fulfillment is tracked separately after payment.
[Tier exclusions] No CLI execution rights, user-host runtime guarantee, external API quota or private repository permissions.
SOL_FOREMAN_PASSPayPal Live / USD — scope of delivery below
Four document updates and up to twelve asynchronous Q&A items over 12 months. Excludes runtime access, API allowance, repository permissions and unlimited engineering.
DOCUMENT_UPDATESASYNC_QARESPONSE_AND_DEPENDENCY_LOG.csvInitial delivery target: 30 business days; 4 document updates over 365 days; async responses for up to 12 Q&A items within a target of 10 business days.
Public access is separate from redistribution permission. Free originals remain free; paid value is editing, crosswalks and reproducible instructions. Private originals, third-party works without permission and personal data are excluded.
The deliverables, SLA and rights boundary stated for this tier apply. Fulfillment is tracked separately after payment.
[Tier exclusions] No CLI execution rights, user-host runtime guarantee, external API quota or private repository permissions.
DEVELOPMENT_PARTNERIndividual quotation and scope agreement
An individual quote from $2500: one workface and one objective, scoping, a pilot using synthetic or licensed material, and bounded handoff support. No direct checkout or promise of production completion.
SCOPING_MEMO.mdPILOT_PLAN.yaml + ACCEPTANCE_CONDITIONS.mdHANDOFF_PACKAGE + REVIEW_SESSIONNo direct checkout; delivery schedule, service period, effort hours and acceptance criteria are set by individual agreement after pre-contract scoping (SCOPING_MEMO.md) and human approval.
Public access is separate from redistribution permission. Free originals remain free; paid value is editing, crosswalks and reproducible instructions. Private originals, third-party works without permission and personal data are excluded.
Delivery follows an individual scope, quote and agreement. This action opens an inquiry, not checkout.
[Tier exclusions] No CLI execution rights, user-host runtime guarantee, external API quota or private repository permissions.
Alongside financial support, technical feedback and hands-on use through public channels help maintain and improve YamRail.
Tell us where complex-system decision handoffs break in your domain, report edge cases, or propose inspection fixtures via our public repository.
Review the public catalog, its dependencies and failure records. Tell us where it helps in your work and where it falls short.
Try the public catalog JSON or the existing CF chat through its consent screen. This candidate page does not change the public services.
Open CF chatPublic preprints; not peer reviewed.