去中心化 · 劳动力互助 · 物理存证 Decentralized · Labor Mutual-Aid · Physical Attestation

生存协议，织网自救 Exchange time,
link surplus.

当自动化系统性替代标准化岗位，人类物理在场依然不可替代。
LinkRSP 为可审计的物理劳务建立积分锚定与互助调度语义——
一套备用型基础设施，为真实劳动确认坐标。 When automation displaces standardized roles, human physical presence remains scarce.
LinkRSP anchors credit semantics to auditable physical work —
backup infrastructure that confirms coordinates for real labor.

阅读白皮书Read Whitepaper 规则引擎Rule Engine 共同建设Contribute

www.linkrsp.com · MIT 开源 · Phase C ✅ 完成 / Phase D 基础设施开建 MIT · Phase C Done / Phase D Infra Started

最新进展：Phase D 接口已上线，语义审计 GET / PATCH 接口完成，人工复核链路就绪，等待复核容量启动 Latest: Phase D APIs complete — semantic audit GET/PATCH endpoints live, human-review pipeline ready, pending capacity

规则执行链Rule Execution R-001–R-010 已具备可运行主链路，R-006 / R-010 接入结算，R-009 接入存证写路径。R-001–R-010 now have runnable main-path coverage, with R-006 / R-010 in settlement and R-009 on attestation writes.

审计与账本Audit & Ledger 审计事件全链路落库，结算保持 preview / commit 分离与幂等写入。Audit events persist end-to-end, with preview/commit separation and idempotent settlement writes.

运行时控制Runtime Controls Phase B 主链路已收口；生产环境须启用 API 共享密钥。R-006 / R-010 参数说明见运维文档。Phase B main path is closed out; production must enable the shared API secret. See ops docs for R-006 / R-010 runtime knobs.

语义审计队列Semantic Audit Queue Phase D 接口已上线：队列表、预筛器与人工复核 GET / PATCH 接口均已完成，等待人工复核容量启动。Phase D APIs live: queue table, PreFilter, and human-review GET/PATCH endpoints are complete, pending review capacity.

核心机制Core Mechanics

协议的四个支柱Four Protocol Pillars

每个模块互相约束，构成可审计的完整语义闭环。 Each module constrains the others, forming a closed auditable semantic loop.

LRS 积分LRS Credits

积分增量 = 物理时长 × 核验强度 × Clip(难度比值, 0.8, 3.0)。积分是权益凭证，不是货币，不由协议托管。 Credits = T_phy × V_bit × Clip(difficulty ratio, 0.8, 3.0). Credits are rights credentials — not currency, no protocol custody.

LRS-1.0

物理存证Physical Attestation

三级核验：V0 声明（0.1）/ V1 BLE+GPS（0.5）/ V2 高保证（1.0）。物理时长是唯一不可虚构的主输入。 Three tiers: V0 declaration (0.1) / V1 BLE+GPS (0.5) / V2 high-assurance (1.0). Physical duration is the only non-fictional primary input.

Handshake v1

双轨社区 S/N MeshS/N Mesh Communities

N 级（孵化期）默认入口；S 级（运行期）经 IPO 式合规跃迁解锁。1+1 Rule：每 UID 每周期仅关联 1S + 1N 社区。 N-type (incubation) is the default entry; S-type (operational) unlocked via IPO-style compliance scan. 1+1 Rule: one UID per 1S + 1N per period.

1+1 Rule

HDGP 治理审计HDGP Governance Audit

HDGP 作为 meta/审计层：输入侧规则扫描 + 输出侧结算叙事审查。LinkRSP 通过适配器接入，保持模块独立。 HDGP acts as the meta/audit layer: pre-publication rule scan + post-settlement narrative review. Integration via adapter keeps domain logic isolated.

HDGP-Core

积分算法Credit Algorithm

LRS-1.0 核心公式LRS-1.0 Core Formula

所有积分增量须通过以下公式计算，参数受治理约束，不作随意租户级调整。 All credit increments must be computed via this formula. Parameters are governance-constrained — no per-tenant overrides.

Credits_delta = (T_phy × V_bit) × Clip((D_base + ΣW_risk) / K_global, 0.8, 3.0)

变量Symbol	含义Meaning	约束Constraint
T_phy	物理时长（分钟）Physical duration in minutes	唯一不可虚构主输入Primary non-fictional input
V_bit	核验强度权重Attestation tier weight	V0 = 0.1 · V1 = 0.5 · V2 = 1.0
D_base	基准难度Baseline difficulty	LRS-1.0 冻结为 1.0Frozen at 1.0 for LRS-1.0
ΣW_risk	风险系数累加Summed risk weights	从 HDGP 原子劳务库选取并审计From HDGP atomic labor library; audited
K_global	全网归一化常数Network normalization constant	创世期 = 1.0；首 1000 S 任务或 90 天后渐变Genesis = 1.0; progressive damping after min(1000 S-tasks, 90d)
Clip(x, 0.8, 3.0)	上下界截断Bounded clipping	0.8 = 尊严底价；3.0 = 高风险溢价上限0.8 = dignity floor; 3.0 = anti-arbitrage cap

⚠ 积分不是货币，不构成法币兑付承诺。法币结算由双方在协议外自行约定，协议不作托管。 ⚠ Credits are not currency and carry no fiat redemption guarantee. Cash settlement is off-protocol — no protocol custody.

管理制度Management Principles

协议如何治理How the Protocol Governs

管理目标不是控制人，而是维护协议履行的公正性。制度以尽量少的干预，保持最大限度的自治。 The goal is not to control people, but to maintain the integrity of protocol execution — minimal intervention, maximum self-governance.

我们不管理「人」，
我们只管理「协议的履行」。 We do not govern people.
We govern the execution of the protocol.

linkrsp 的管理不以行政控制为目的，而是为了维护物理规则的公正性。 LinkRSP governance exists not for administrative control, but to maintain the fairness of physical rules.

— 架构师声明 ·Architect Statement · 管理制度草案 v1.0 AlphaManagement Regs v1.0 Alpha

①

1+1 双轨约束1+1 Dual-Track Constraint

每个 UID 每周期仅允许关联 1 个 S 级（强任务）社区 + 1 个 N 级社区。防止精力稀释与信用投机，保持在生存层的专注与责任。 Each UID may associate with 1 S-type (hard-task) + 1 N-type community per period — preventing effort dilution and credit speculation.

②

社区 IPO 跃迁Community IPO Transition

N 级（孵化期）升至 S 级（运行期）须通过：成员基数与存证任务量硬门槛 + HDGP 伦理合规扫描 + Judge 板块公示与共识校验。 N → S transition requires: member/task hard thresholds + HDGP ethical scan + Judge board public review and consensus verification.

③

金钱交易不干预Economic Non-Interference

协议不干预用户间法币交易，允许双方自主商定报酬。LinkRSP 不提供资金托管与担保；现金层风险由用户自行承担。 The protocol does not intervene in fiat transactions between users. No custodial services — cash-layer risk is borne by parties directly.

④

动态熔断与红线惩罚Circuit Breaker & Red-Line Penalty

网关监测虚假任务或数据通胀时自动锁定账户。S 级社区触碰 HDGP 伦理红线则强制降级至 N 级，并公开标记发起人信用记录。 Gateway auto-locks on fake tasks or data inflation. S-type communities that breach HDGP ethical red lines are forced back to N-type with public credit flagging.

⑤

规则透明 · 可预期Rule Transparency & Predictability

社区「宪章」（自治规则）通过 Judge 板块公示后对成员生效；重大修订须重新公示。成员对其生存环境有权可预期。 Community charters take effect after Judge board publication; major amendments require re-publication. Members have a right to predictable conditions.

实施路线图Implementation Roadmap

分阶段交付Phased Delivery

成本递延策略：每阶段设有明确前置条件，不抢跑，不烧钱。 Cost postponement strategy: each phase has clear gate conditions — no premature execution, no wasted spend.

✓

已完成Done

Phase A — 规范 & 治理基础Phase A — Specs & Governance

50 条规则 YAML、审计事件模式、时间窗口约定、算法规格、实施计划、管理制度草案。50 rule YAMLs, audit event schema, time conventions, algorithm spec, implementation plan, management regs.

✓

已完成Done

Phase B — R 类规则 MVPPhase B — R-Class Rules MVP

Go + PostgreSQL + Supabase；R-001–R-010 可运行主链路已收口；R-006 / R-010 运行时参数说明见运维文档。共享密钥在生产环境必设。Go + PostgreSQL + Supabase; R-001–R-010 runnable main path is closed out; see ops docs for R-006 / R-010 runtime knobs. Shared secret is mandatory in production.

✓

已完成Done

Phase C — 账本 & 结算Phase C — Ledger & Settlement

只追加事件账本、结算预览 / 提交 API 与幂等写入已收口；端到端试点链路已跑通并落库，可回放验证。Append-only ledger, settlement preview/commit, and idempotent writes are complete; the end-to-end pilot loop is proven and replayable.

进行中In Progress

Phase D — S 类规则（无 LLM）Phase D — S-Class "No LLM" Mode

语义审计作“可插拔通路”：Postgres 队列 + 触发词预筛 + 人工复核写回。系统不定义社区 SOP，仅提供可回放证据与最小网关约束。A pluggable semantic-audit path: Postgres queue + trigger-word screening + human review write-back. The system does not prescribe community SOP — only replayable evidence and minimal gateway constraints.

成本门控Cost-Gated

Phase E — LLM 批处理集成Phase E — LLM Batch Integration

S 类规则 LLM Oracle；需稳定预算 + few-shot 校准样本 + 隐私策略。LLM Oracle for S-class rules; requires stable budget, few-shot calibration samples, privacy strategy.

延后Deferred

Phase F — HDGP Engine 接入Phase F — HDGP Engine Integration

LinkRSP 审计事件 → HDGP Rule Engine 适配器；需接口合约冻结后启动。LinkRSP audit events → HDGP adapter; starts after interface contract is frozen.

开放共建Open Contribution

共同建设
LinkRSP Build LinkRSP
Together

规格已冻结，后端主链路已启动并持续接线中。当前最需要的是把规则执行、结算闭环、审计与真实试跑继续推到可交付状态。 Specs are frozen and the backend main path is live and still being wired. The highest-value work now is pushing rule execution, settlement loops, auditing, and real trials toward delivery.

LinkRSP GitHubLinkRSP GitHub HDGP-CoreHDGP-Core 联系创始人Contact Founder

Go 工程师Go Engineers

当前主线是把 R-001–R-010、结算 preview / commit、审计落库与内部查询继续打磨成稳定闭环。Go + PostgreSQL，只追加账本，规格冻结，可直接从现有 API 与规则实现接手。 The current mainline is stabilizing R-001–R-010, settlement preview/commit, audit persistence, and internal queries into a reliable loop. Go + PostgreSQL, append-only ledger, specs frozen — contributors can plug directly into the current API and rule implementation.

最急需Most Needed

规则引擎贡献Rule Engine Extension

规则引擎已达 50 条，欢迎贡献 few-shot 示例优化、false positive 场景分析、或新场景规则提案。 Rule engine has reached 50 rules. Contribute few-shot example improvements, false-positive analysis, or new rule proposals.

YAML · LLM

红队 & 压测Red-Team & Stress Testing

优先检验写接口门禁、规则边界、preview / commit 幂等与异常时间窗口。边界报告越早出现，主网上线前的补洞成本越低。 Priority targets are write-route gating, rule boundaries, preview/commit idempotency, and abnormal time windows. Early boundary reports reduce the cost of patching before production rollout.

安全研究Security Research

翻译 & 文档Translation & Docs

将核心规格翻译为英文（部分已有双语），或协助整理文档结构。让协议对更广泛社区可读。 Translate core specs to English (some already bilingual), or help organize doc structure — making the protocol readable to a wider community.

MIT · Open

生存协议，织网自救 Exchange time,link surplus.

协议的四个支柱Four Protocol Pillars

LRS 积分LRS Credits

物理存证Physical Attestation

双轨社区 S/N MeshS/N Mesh Communities

HDGP 治理审计HDGP Governance Audit

LRS-1.0 核心公式LRS-1.0 Core Formula

协议如何治理How the Protocol Governs

1+1 双轨约束1+1 Dual-Track Constraint

社区 IPO 跃迁Community IPO Transition

金钱交易不干预Economic Non-Interference

动态熔断与红线惩罚Circuit Breaker & Red-Line Penalty

规则透明 · 可预期Rule Transparency & Predictability

分阶段交付Phased Delivery

Phase A — 规范 & 治理基础Phase A — Specs & Governance

Phase B — R 类规则 MVPPhase B — R-Class Rules MVP

Phase C — 账本 & 结算Phase C — Ledger & Settlement

Phase D — S 类规则（无 LLM）Phase D — S-Class "No LLM" Mode

Phase E — LLM 批处理集成Phase E — LLM Batch Integration

Phase F — HDGP Engine 接入Phase F — HDGP Engine Integration

关键规范文档Key Specifications

共同建设LinkRSP Build LinkRSPTogether

Go 工程师Go Engineers

规则引擎贡献Rule Engine Extension

红队 & 压测Red-Team & Stress Testing

翻译 & 文档Translation & Docs

生存协议，织网自救 Exchange time,
link surplus.

共同建设
LinkRSP Build LinkRSP
Together