尼赫罗
- 作者仓库星标 23
- 许可证 MIT
- 作者仓库 asi
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 100 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @plurigrid · v0.1.0 · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
# nhero
Aftermarket cybernetic network device. One lowercase word.
nhero treats every pill dispenser as a network device. The same way Pi-hole intercepts DNS queries and decides what passes through, nhero intercepts medication scheduling commands and routes them through a scrambled, GF(3)-conserved, confidential-asset-backed supply chain.
## Hierarchy
```
nhero/ ← umbrella (this skill)
├── killdispenser/ ← fundamental primitive: the piehole in every device
├── hero-dispenser-mod/ ← Hero Health Model 100 specific implementation
├── nhero-pyhole/ ← DNS-style medication routing layer
├── nhero-scramble/ ← derangement-based name scrambling
├── nhero-confidential/ ← Twisted ElGamal supply tracking on Aptos
└── nhero-nurse/ ← nurse approval email automation
```
## Concepts
### killdispenser
The fundamental piehole in every device. Like `kill(1)` sends signals to processes, killdispenser sends signals to dispensing slots. Like Pi-hole blocks DNS, killdispenser blocks unauthorized dispense events. Every nhero device has a killdispenser — it's the control plane.
### PyHole Model
Pi-hole blocks ads at DNS level. nhero blocks/routes medications at schedule level:
- **Blocklist** = controlled substances requiring nurse approval
- **Allowlist** = OTC supplements (Magnesium, Zinc, Ginkgo, Caffeine)
- **Upstream** = Hero cloud API (intercepted via mitmproxy)
- **Local DNS** = scramble index (letter → medication lookup)
### Scramble Index (Derangement)
No medication maps to its own initial letter. Full derangement:
| Slot | Medication | GF(3) |
|------|-----------|-------|
| q | Vyvanse | -1 |
| x | Magnesium | 0 |
| y | Zinc | +1 |
| k | Ginkgo | -1 |
| u | Caffeine | 0 |
Conservation: Q(-1) + X(0) + Y(+1) + K(-1) + U(0) = **-1** = H world trit
### Confidential Assets (Huber-Duncan)
`0x7::confidential_asset` on Aptos testnet:
- Twisted ElGamal encrypts supply counts
- ZK range proofs verify `remaining > threshold` without revealing count
- Nurse holds auditor key, never sees medication names or exact counts
- Each dispense = confidential withdraw of 1
## Topos-MCP Server
9 tools as morphisms in the category of dispenser states.
Registered as `hero-topos` MCP server (stdio JSON-RPC).
## Hardware Target
- **Hero Model 100** (FCC ID: 2AN4DM115, OEM: Xiamen Zayata Technology)
- PCB revisions: ZA-D102LCD_V2.1 (UI), 1027306-V46 (logic), ZA-1200DCM/2.0 (USB)
- OMRON G5V-1 relay, WiFi 2.4GHz, PCB trace antenna at ANT1
- Test points TP1-TP4 on USB daughter board (likely UART)
## World
- Letter: H (index 7, GF(3) -1, Chain 1 Witness-Bridge)
- Email: `mantissa+hero-h@plurigrid.com`
- Nurse: `mantissa@gmail.com` / `ies@plurigrid.com`
章节与文件索引
按说明文件中的顺序排列。
杀戮发射器
PyHole模型
打乱索引(混乱)
机密资产 (Huber-Duncan)
拓扑-MCP服务器
文件/命令 -> kill(1) · 0x7::confidential_asset · remaining > threshold · hero-topos · mantissa+hero-h@plurigrid.com · mantissa@gmail.com · ies@plurigrid.com
内容校验值 -> 2a66f83acd53
当前原文的自动摘译,尚未人工审校。
杀戮发射器
每个设备中的基本部分。就像
kill(1)向进程发送信号一样,killdispenser向分配槽发送信号。与 Pi-hole 阻止 DNS 一样,killdispenser 也阻止未经授权的分配事件。每个 nhero 设备都有一个killdispenser——它是控制平面。PyHole模型
Pi-hole 在 DNS 级别拦截广告。 nhero 在计划级别阻止/路由药物: 阻止列表 = 需要护士批准的受控物质 允许列表 = OTC 补充剂(镁、锌、银杏、咖啡因) 上游 = Hero 云 API(通过 mitmproxy 拦截) 本地 DNS = 扰乱索引(字母 → 药物查找)
打乱索引(混乱)
没有药物可以映射到其自己的首字母。完全混乱:槽·药物·GF(3) q·Vyvanse·-1 x·镁·0 y·锌·+1
机密资产 (Huber-Duncan)
Aptos 测试网上的
0x7::confidential_asset:Twisted ElGamal 加密供应计数 ZK 范围证明验证remaining > threshold,无需泄露计数 护士持有审核员密钥,从不看到药物名称或确切计数 每次分配 = 保密提取 1拓扑-MCP服务器
9 个工具作为分配器状态类别中的态射。注册为
hero-toposMCP 服务器(stdio JSON-RPC)。