Skip to content

Jordanwei1/jiaojie-skill

jiaojie

Flagged

Create or receive human-first AI task handoffs across chats, models, devices, and languages. Use when the user asks to hand off, export context, resume from a handoff, switch sessions while preserving work, says "交接一下", "接收交接", or supplies handoff.md, handoff.zip, handoff-audit.zip, an LCH Bundle/T0 package, OCH Snapshot, or LTM Packet. Default to one readable handoff.md; upgrade to handoff.zip only when required files must travel, and to handoff-audit.zip only for formal audit, cross-organization delivery, or proof. Preserve current intent, stop point, next action, decisions, constraints, rejected and failed paths, answered questions, materials, omissions, and revalidation needs. Do not use for generic summaries, memory lookup, hidden reasoning, completed trivial chats, or after the user declines.

FileKindSize
SKILL.mdskill md8.1 KB
agents/openai.yamlconfig223 B
assets/hero-source.pngbinary1.3 MB
assets/hero.gifbinary1.2 MB
assets/profiles/materiality-v1.jsonconfig853 B
assets/protocol-version.jsonconfig2.6 KB
assets/registry/iana-language-subtag-registry-2026-08-08.txtmarkdown714.6 KB
assets/registry/iana-language-tag-extensions-registry-2014-04-02.txtmarkdown1.0 KB
assets/registry/profile-feature-registry-v0.1.jsonconfig3.3 KB
assets/registry/registry-lock.jsonconfig1.2 KB
assets/registry/schema-catalog-v0.1.jsonconfig4.1 KB
assets/schemas/action-graph.schema.jsonconfig5.6 KB
assets/schemas/common.schema.jsonconfig25.7 KB
assets/schemas/derived-digest-vector.schema.jsonconfig1.5 KB
assets/schemas/detached-envelope.schema.jsonconfig799 B
assets/schemas/event.schema.jsonconfig4.5 KB
assets/schemas/language-unicode-vector.schema.jsonconfig8.6 KB
assets/schemas/legacy-conversion-report.schema.jsonconfig4.4 KB
assets/schemas/manifest.schema.jsonconfig6.6 KB
assets/schemas/materiality-profile.schema.jsonconfig1.6 KB
assets/schemas/profile-feature-registry.schema.jsonconfig7.3 KB
assets/schemas/receipt.schema.jsonconfig15.6 KB
assets/schemas/registry-lock.schema.jsonconfig1.9 KB
assets/schemas/schema-catalog.schema.jsonconfig1.7 KB
assets/schemas/state.schema.jsonconfig11.9 KB
assets/schemas/t0-control.schema.jsonconfig2.7 KB
assets/schemas/vector-catalog.schema.jsonconfig5.3 KB
assets/schemas/verification-result.schema.jsonconfig24.2 KB
assets/templates/approval-statement.template.jsonconfig1.3 KB
assets/templates/approval-verification.template.jsonconfig1.6 KB
assets/templates/bundle-HANDOFF.template.mdmarkdown57 B
assets/templates/conversion-report.template.jsonconfig1.2 KB
assets/templates/handoff.template.mdmarkdown1.7 KB
assets/templates/manifest.template.jsonconfig8.6 KB
assets/templates/receipt.template.jsonconfig3.2 KB
assets/templates/t0-control.template.jsonconfig6.4 KB
assets/templates/t0-package.template.mdmarkdown337 B
assets/templates/warm-state.template.jsonconfig10.2 KB
assets/vectors/derived-digests-v1-001.jsonconfig10.8 KB
assets/vectors/index.jsonconfig2.1 KB
assets/vectors/jcs-sha256-basic-001.jsonconfig495 B
assets/vectors/language-unicode-v1-001.jsonconfig9.9 KB
assets/vectors/review-projection-v1-minimal-001.jsonconfig19.0 KB
examples/README.mdmarkdown1.4 KB
examples/business/business-external-state/case.jsonconfig559 B
examples/business/business-external-state/expected-next-action.mdmarkdown111 B
examples/business/business-external-state/expected-receipt.mdmarkdown342 B
examples/business/business-external-state/gold.jsonconfig498 B
examples/business/business-external-state/handoff.mdmarkdown1.8 KB
examples/business/business-external-state/source.mdmarkdown730 B
examples/coding/coding-cross-language/case.jsonconfig603 B
examples/coding/coding-cross-language/expected-next-action.mdmarkdown108 B
examples/coding/coding-cross-language/expected-receipt.mdmarkdown342 B
examples/coding/coding-cross-language/gold.jsonconfig495 B
examples/coding/coding-cross-language/handoff.mdmarkdown2.0 KB
examples/coding/coding-cross-language/source.mdmarkdown864 B
examples/general-chat/general-chat-mixed-constraints/case.jsonconfig577 B
examples/general-chat/general-chat-mixed-constraints/expected-next-action.mdmarkdown116 B
examples/general-chat/general-chat-mixed-constraints/expected-receipt.mdmarkdown347 B
examples/general-chat/general-chat-mixed-constraints/gold.jsonconfig508 B
examples/general-chat/general-chat-mixed-constraints/handoff.mdmarkdown1.8 KB
examples/general-chat/general-chat-mixed-constraints/source.mdmarkdown745 B
examples/index.jsonconfig4.9 KB
examples/learning/learning-intent-change/case.jsonconfig568 B
examples/learning/learning-intent-change/expected-next-action.mdmarkdown109 B
examples/learning/learning-intent-change/expected-receipt.mdmarkdown342 B
examples/learning/learning-intent-change/gold.jsonconfig496 B
examples/learning/learning-intent-change/handoff.mdmarkdown1.8 KB
examples/learning/learning-intent-change/source.mdmarkdown714 B
examples/product-design/product-design-parallel/case.jsonconfig572 B
examples/product-design/product-design-parallel/expected-next-action.mdmarkdown121 B
examples/product-design/product-design-parallel/expected-receipt.mdmarkdown342 B
examples/product-design/product-design-parallel/gold.jsonconfig508 B
examples/product-design/product-design-parallel/handoff.mdmarkdown1.8 KB
examples/product-design/product-design-parallel/source.mdmarkdown732 B
examples/research/research-partial/case.jsonconfig553 B
examples/research/research-partial/expected-next-action.mdmarkdown114 B
examples/research/research-partial/expected-receipt.mdmarkdown347 B
examples/research/research-partial/gold.jsonconfig506 B
examples/research/research-partial/handoff.mdmarkdown1.8 KB
examples/research/research-partial/source.mdmarkdown718 B
examples/writing/writing-authority/case.jsonconfig578 B
examples/writing/writing-authority/expected-next-action.mdmarkdown94 B
examples/writing/writing-authority/expected-receipt.mdmarkdown342 B
examples/writing/writing-authority/gold.jsonconfig481 B
examples/writing/writing-authority/handoff.mdmarkdown1.8 KB
examples/writing/writing-authority/source.mdmarkdown703 B
references/conformance.mdmarkdown42.5 KB
references/convert-legacy.mdmarkdown14.0 KB
references/domain-business.mdmarkdown3.3 KB
references/domain-coding.mdmarkdown3.4 KB
references/domain-general-chat.mdmarkdown3.2 KB
references/domain-learning.mdmarkdown3.2 KB
references/domain-product-design.mdmarkdown3.3 KB
references/domain-research.mdmarkdown3.3 KB
references/domain-writing.mdmarkdown3.2 KB
references/export-workflow.mdmarkdown14.9 KB
references/multilingual-workflow.mdmarkdown9.6 KB
references/profiles.mdmarkdown21.1 KB
references/protocol-core.mdmarkdown28.7 KB
references/receive-workflow.mdmarkdown23.2 KB
references/result-model.mdmarkdown22.3 KB
references/runtime-capabilities.mdmarkdown6.8 KB
references/security-boundary.mdmarkdown8.8 KB
references/simple-workflow.mdmarkdown7.0 KB
references/terminology.mdmarkdown13.3 KB
references/threat-model.mdmarkdown20.1 KB
references/verify-structure-workflow.mdmarkdown21.9 KB
references/wire-format.mdmarkdown44.0 KB
scripts/_vendor/lch/__init__.pyscript1.4 KB
scripts/_vendor/lch/canonicalize.pyscript7.6 KB
scripts/_vendor/lch/cli.pyscript10.2 KB
scripts/_vendor/lch/converters.pyscript46.0 KB
scripts/_vendor/lch/language.pyscript27.7 KB
scripts/_vendor/lch/package.pyscript56.8 KB
scripts/_vendor/lch/projection.pyscript22.7 KB
scripts/_vendor/lch/registry.pyscript7.9 KB
scripts/_vendor/lch/schema.pyscript19.5 KB
scripts/_vendor/lch/security.pyscript7.2 KB
scripts/_vendor/lch/simple.pyscript36.6 KB
scripts/_vendor/lch/util.pyscript14.7 KB
scripts/_vendor/lch/validate.pyscript128.4 KB
scripts/convert_handoff_md.pyscript207 B
scripts/convert_ltm.pyscript201 B
scripts/convert_och.pyscript205 B
scripts/handoff.pyscript190 B
scripts/pack_handoff.pyscript175 B
scripts/project_check.pyscript3.2 KB
scripts/scan_sensitive.pyscript183 B
scripts/validate_handoff.pyscript180 B
scripts/verify_handoff.pyscript188 B

references/runtime-capabilities.md

View on GitHub
# Runtime Capabilities

> The T0-T3 modes below describe the full LCH 0.1 audit protocol. They no longer
> choose the ordinary product format. For ordinary work, use
> `simple-workflow.md`: Markdown by default, ZIP only for required files, and an
> audit ZIP only when proof must travel.

Read this reference before `EXPORT`, `RECEIVE`, `VERIFY_STRUCTURE`, or `CONVERT_LEGACY` when runtime support is uncertain.

Treat this file as operational guidance. Do not derive new wire fields from its headings or checklists.

## Contents

- [Detect capabilities](#detect-capabilities)
- [Choose the transport mode](#choose-the-transport-mode)
- [Operate in T0](#operate-in-t0)
- [Operate in T1](#operate-in-t1)
- [Operate in T2](#operate-in-t2)
- [Operate in T3](#operate-in-t3)
- [Apply capability degradation](#apply-capability-degradation)
- [Keep profiles and results separate](#keep-profiles-and-results-separate)

## Detect capabilities

Inspect the current runtime. Do not infer capabilities from a product name.

- Check whether the runtime can read and write plain text.
- Check whether it can upload and open attachments.
- Check whether it can access a filesystem safely.
- Check whether it can run the Skill and deterministic scripts.
- Check whether it can process every required modality.
- Check whether it can process the authoritative source language.
- Check available context, object, archive, and token limits.
- Check whether tools and side effects can remain disabled during inspection.
- Record the capabilities actually used for this run.

Do not change semantic fields because a runtime is weaker or stronger.

## Choose the transport mode

Use the lowest mode that preserves every material object and state record.

| Mode | Available runtime support | Use |
| --- | --- | --- |
| T0 | Text only | One self-describing Markdown package |
| T1 | Attachments | One intact Bundle attachment, normally ZIP |
| T2 | Filesystem | A structured directory or ZIP Bundle |
| T3 | Scripts and Skill | Deterministic packing, hashing, validation, and conversion |

Do not label a mode as better evidence. A transport mode is not a verification result.

## Operate in T0

- Use the fixed `LCH-T0 <major.minor>` framing.
- Preserve the exact JCS control bytes and declared byte length.
- Preserve the canonical ordered embedded-object manifest.
- Encode embedded binary objects with unpadded RFC 4648 Section 5 base64url.
- Use fixed 4096-character chunks, explicit chunk indexes, lengths, and raw SHA-256.
- Keep the matching `LCH-T0-HUMAN-VIEW` review projection.
- Keep all material text and small artifacts inside the package.
- Refuse silent truncation when the package exceeds the target context.

When receiving T0 without a deterministic preprocessor, do not mint byte or security
result objects. Require the Receiver Receipt to show `BYTE_CONSISTENCY: NOT_RUN`, leave
`verification_result_refs.security_run` null, add an issue that security verification
did not run, and set `processing_status: SECURITY_LIMITED`. A Runtime-enforced text-only
posture may use the core one-response exception; inability to enforce isolation sets
`blocking_reasons[].code: SECURITY_BLOCKED` while `processing_status` remains
`SECURITY_LIMITED`. Keep tools and side effects disabled while reading. In `EXPORT`, no
deterministic preprocessor means no sealed native T0: produce only an explicit unverified
draft and no Receipt. In standalone `VERIFY_STRUCTURE`, report that the check did not run
without minting its result or a Receiver Receipt.

## Operate in T1

- Carry the same native Bundle used by T2 as one intact attachment, normally a ZIP.
- Keep `MANIFEST.json` as the only integrity root and preserve the complete logical object layout.
- Require every material object to be committed by the Manifest.
- Reject or ignore loose, unrooted attachments.
- Fall back to T0 when the runtime cannot preserve or reopen the intact Bundle.
- Verify that the runtime can open the Bundle and each required object before claiming it was processed.
- Preserve original bytes even when a derived text view exists.
- Set `processing_status` to `MODALITY_LIMITED` when a required attachment cannot be read.

Do not replace an unread image, audio file, video, or binary document with its summary.

## Operate in T2

- Use the Bundle layout and treat `MANIFEST.json` as its only integrity root.
- Check resource limits, paths, links, collisions, and archive depth before extraction.
- Recompute object hashes and `canonical_state_digest` when deterministic support exists.
- Treat `HANDOFF.md` as a derived view.
- Fail the derived view when its package or state summary conflicts with the Manifest.
- Keep `envelopes/` outside the Manifest root.

Do not use a local absolute path as the only location for a required object.

## Operate in T3

- Use the installed Skill only as workflow guidance.
- Use deterministic scripts for packing, hashing, validation, and frozen legacy mappings.
- Pin required canonicalization, Unicode, and registry versions.
- Validate before committing output.
- Keep independent result roles separate from the Producer.

Do not let script availability upgrade `CONTENT_COVERAGE_CLAIM`, origin, approval, or continuity results.

## Apply capability degradation

- Use `PARTIAL` when a known material source or object is missing.
- Use `UNKNOWN` when the source boundary itself is unknown.
- Keep package `content_coverage` unchanged when only the Receiver is limited.
- Lower Receipt `processing_coverage` when the Receiver cannot process required content.
- Use `LANGUAGE_LIMITED` when the authoritative language cannot be handled reliably.
- Use `MODALITY_LIMITED` when a required modality cannot be read.
- Use `PACKAGE_LIMITED` when local resource limits block safe processing.
- Use `SECURITY_LIMITED` with a precise issue when a required security scan did not run but the Runtime still enforces text-only isolation.
- Add `blocking_reasons[].code: SECURITY_BLOCKED` and block continuation when the required isolation posture itself cannot be enforced; keep `processing_status: SECURITY_LIMITED`.
- Set `continuation_status: BLOCKED` when a selected action lacks a required capability.

Never delete core fields, rewrite state, or turn a failure into success to fit the platform.

## Keep profiles and results separate

- Resolve artifact Profiles from the verified release registry. Release `0.1.0`
  supports core Markdown and self-contained, qualifies multilingual only for its
  registered vector scope, and marks confidential transport unsupported and
  non-selectable.
- Treat `LEGACY_CONVERTER` as an implementation capability.
- Treat `RECEIPT_CONFORMANCE` as a run result.
- Treat Profile conformance as a prerequisite, not a Continuity Eval result.

Do not claim that any runtime, Profile, model, language pair, or transport mode is currently verified unless an applicable independent result object and published evidence say so.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall