تشغيل أي مهارة في Manus بنقرة واحدة

telemetry-pipeline

النجوم١٩

التفرعات١

آخر تحديث١٩ يوليو ٢٠٢٦ في ١٦:٠٩

Use when working on the silken_net telemetry / Proof-of-Growth pipeline — the uplink→verification→minting flow (CoAP intake → UnpackTelemetryWorker / TelemetryUnpackerService → IoTeX verify → Chainlink oracle → mint), the Sidekiq strict-priority queues, TelemetryLog (RANGE-partitioned, KENOSIS — validations live in valid_sensor_data?, not the model), and the dual-computation integrity (server Float Lorenz ≡ firmware mruby). Knows the gotchas — DID=0 in a batch is DEAD (ARCH.54: Queen pulse rides the signed QATT-v2 header → enqueue_envelope_health, both eras drop DID=0), oracle_status_*? enum methods, strict queue drain (uplink fully before alerts), find_with_partition_pruning. Routes to CLAUDE.md §5/§6 + the 05_02 canon, does not restate. Examples: "add a telemetry field", "change minting logic / guards", "why is an alert delayed", "decode the uplink packet", "why does server Z differ from device Z".

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

Alexey-Lukin

Alexey-Lukin/silken_net

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name

telemetry-pipeline

description

Telemetry Pipeline

SSOT Documents — Read These First

Document	What it covers
`CLAUDE.md §1`	Proof of Growth pipeline — full A→D flow (sense→…→mint SCC)
`CLAUDE.md §5`	Sidekiq strict-priority queues + Lorenz/StatusByte + AES invariants
`CLAUDE.md §6`	Telemetry cross-domain gotchas (oracle_status prefix · KENOSIS · partitions)
`docs/05_02_Proof_of_Growth_Pipeline.md`	Exact worker ordering with queue assignments
`docs/05_03_Tokenomics_SCC_and_SFC.md`	Growth points, SCC minting (slashing → `05_05`)
`docs/03_05_Hardware_Symmetric_Crypto_and_Security.md §3`	AES decrypt chain, key management

Gotchas Not Obvious From Docs

DID 0x00000000 in a batch is DEAD (ARCH.54, 2026-07-03) — the old Queen-Sentinel pseudo-tree is dropped on BOTH paths (ECB and CCM): the pulse rides the SIGNED QATT-v2 envelope header (8B health block, firmware/common/queen_attest.h) → UnpackTelemetryWorker#enqueue_envelope_health → GatewayTelemetryWorker. Never re-add gateway metrics as a fake tree — it eats a CIFO slot, breaks the CCM stride, and health without a valid Ed25519 must not exist (masking-attack). Canon: 03_02 §7 + 06_08 §1.3.
oracle_status prefix — call log.oracle_status_fulfilled? not log.oracle_status == "fulfilled". String-backed enum with oracle_status_ prefix.
Dual computation — server Lorenz (Float) must match firmware mruby (Float). Was BigDecimal before FW.7 — old to_d code is a bug now.
Queue drain is strict — uplink (#1) drains COMPLETELY before alerts (#2). Telemetry flood blocks alerts. By design.
Validations removed from TelemetryLog — KENOSIS TITAN. Check is in TelemetryUnpackerService.valid_sensor_data?. Don't add validations back to model.
Partition-aware lookups — TelemetryLog RANGE-partitioned by created_at. Always use find_with_partition_pruning(id, created_at).
«Wire = вхід GP» contract (E.63 (г), wire-rev2.1) — the CCM frame carries BOTH dT fields: raw (bytes 12..13, diagnostics/server-EMA) and ema_delta_t_s (bytes 20..21) = the EXACT number metabolic_health consumed on the device → check_metabolic_divergence! recomputes GP statelessly via Attractor.expected_homeostasis_gp(ema) (byte-identical mirror of bio_contract.rb §4.3 — edit the formula/thresholds THERE first, mirror second, regen lorenz_bytecode.h). The branch is observational (warn+metric) until the bench calibrates DELTA_T_FAST_S/DELTA_T_SLOW_S; ema_delta_t_s is transient (stripped pre-persist, like lorenz_temperature_c/device_z). ECB frames carry no ema → branch honestly skips. Canon: 03_04 §4.3 + 03_01 §13.6.
firmware_version_id = wire-ЗВІТ, не FK (SEC.20, 2026-07-12) — post-SEC.20 семантика [semantic:1|reverted:1|contract_id&0x3FFF] (дзеркало firmware/common/fw_report.h): читай через TelemetryLog#firmware_report_semantic?/reverted?/contract_id (id ПО МОДУЛЮ 14 біт — НЕ join і не пряме порівняння з BioContractFirmware.id); legacy-кадри (без semantic-біта) несуть C-image константу — contract-версії НЕ мають. reverted? → EwsAlert firmware_reverted (термінальний: re-issue лише версією > спаленої — 03_06 §4 bump-інваріант).
TelemetryLog тепер несе MRV-lineage сліди (ARCH.12/E.60, 2026-07-19) — mint-інтенти отримують детерміновані вікна вимірів (Wallet watermark-курсор → telemetry_window_* на tx), а pin-воркер стемпить telemetry_logs.{archive_root, merkle_leaf} (E.60 Фаза 1б). Перший AR-колбек моделі: before_update seal-guard — мутація z_value/bio_status/created_at/tree_id стемпнутого рядка = raise (KENOSIS недоторканий: intake = insert_all, колбек не стріляє; oracle_status/verified_by_iotex — не leaf-поля, вільні). Leaf-формула One-Home = 05_02 §E.60 (Mrv::TelemetryLeaf, LEAF_VERSION). Не додавай у leaf-payload нове поле без LEAF_VERSION-bump.
Device-event 0x57 = ОКРЕМИЙ L1-канал, не телеметрія (SEC.21, 2026-07-12) — рідкісні security-події (canary-trip) НЕ їдуть телеметрійним трактом: окремий CoAP PUT device/event/<uid> → DeviceEventWorker (не UnpackTelemetryWorker). Королева підписує cleartext-конверт власним EDSK (тег SLKN-QEVT1, окремий від QATT2) → worker verify gateway-origin (HardwareKey.ed25519_public_key_hex, як QATT-батч), Rails LoRa-ключа НЕ торкається. Не плутай з CCM blind-courier телеметрії (там per-DID decrypt на Rails); тут — L1-підпис Королеви. Trust L1-observational, НІКОЛИ не money-path. Дім 03_05 §2.2а + 03_02 §7а.

Common Tasks

Add telemetry field: firmware pack → TelemetryUnpackerService unpack → DB migration → Phlex dashboard component → update docs/05_02
Change minting logic: BlockchainMintingService → the 2-guard oracle chain (IoTeX + oracle_status) protects PATH 1 only (latent — ARCH.53 §🗄️: dispatch = local marker, DON-callback unwired, closure refused 2026-07-19); KYC (Hadron) guards ALL paths and is the sole PATH-2 perimeter (live PATH 2 mint = optimistic, KYC-only; L0-custodial + ex-post clawback). Service-home = 04_02 §4; tokenomics course → 05_03 (see web3-pipeline skill)

المزيد من هذا المستودع

نفس المستودع

frontend

Alexey-Lukin/silken_net

Use when working on the silken_net frontend — the Phlex component tree (app/views/components/ + shared/ui|iot|web3/), the Tailwind v4 @theme design-token system (gaia-* surfaces/text, status-*, token-* blockchain, gaia-input-*), the ApplicationComponent base (the tokens() TailwindMerge wrapper + class-autoscoped t() i18n + Turbo-broadcast-safe delegated helpers), the 8 Stimulus controllers, and Turbo Streams/Frames. Knows the non-obvious gotchas — NO tailwind.config.js (SSOT = app/assets/tailwind/application.css @theme), raw Tailwind forbidden in shared components (use status-*/gaia-* tokens), register a new font-size in CUSTOM_TEXT_SCALE for TailwindMerge, NO DB queries in a Phlex initialize, t('.key') autoscopes by class name, specs default to English, Turbo broadcast_* runs in model context (no current_user). Routes to 04_04 (the design-system SSOT) + CLAUDE.md §6, does not restate. Examples: 'add a Phlex component', 'add a design token', 'why isn't my color class merging', 'add a Stimulus controller', 'i1

2026-07-1919

web3-pipeline

Alexey-Lukin/silken_net

Use when working on the silken_net Web3 / on-chain surface — the 12-chain Proof-of-Growth pipeline (app/services/ + workers): SCC/SFC Solidity contracts, batchMint + Binary-Search poisoned-record isolation, the BlockchainTransaction AASM (incl. manual_review double-spend guard), minting guard-clauses (IoTeX / Chainlink / Hadron KYC), Dynamic Tax, slashing / penalty-factor de-correlation, Solana micro-rewards (Ed25519, batch payouts), DAO / Governor / Timelock, WEB3_STRICT_MODE. Routes to CLAUDE.md §1 (12-chain overview) + §6 (web3 gotchas) + the 05_01..05_06 canon (solc One-Home = 05_03), does not restate. Examples: "add a chain integration", "change the minting threshold", "why is a tx stuck in manual_review", "batchMint reverts on dry-run", "edit the slashing penalty", "Solana reward formula / batch payout".

2026-07-1919

backend

Alexey-Lukin/silken_net

Use when working on the silken_net Rails 'Web2 core' — data models (app/models/ + concerns), the REST API v1 controllers (app/controllers/api/v1/), auth/RBAC (Bearer + salt-bound session cookie, M2M Ed25519, Pundit policies), the non-money services/workers (app/services/, app/workers/), and the MaintenanceRecord / Evidence-Protocol domain. Knows the non-obvious gotchas — role enum prefix:true (role_admin?, NOT admin?; no 'patrol' role exists), the IDOR sibling-guard for client-supplied FKs (foreign-but-existing → 404, missing → 422), the session[:ps] password-salt stamp, M2M token = full org-admin scope (SEC.16), Idempotency-Key → 400 not 422, the webhook HMAC fail-closed pattern, exact HKDF info-strings per owner type, Gateway#online? = config_sleep_interval_s * 1.2, self.primary_key = 'id' on partitioned models, Auditable = after_update_commit + saved_change (NOT AASM after_all_transitions), the FactoryBot initialize_with reuse for Tree's auto-created wallet/calibration. Routes to the 04_01/04_02/04_03/04_0

2026-07-1919

ssot-maintenance

Alexey-Lukin/silken_net

Use when working on the SSOT docs (docs/NN_NN_*.md) — editing or creating a canon doc, hunting or fixing SSOT drift, adding a docs linter / CI gate, checking where a fact canonically lives, or publishing canon to the GitHub wiki. Operational playbook for docs:check_refs / docs:toc / tracker:check / wiki:sync; defers the STANDARD itself to 00_02 + 00_06. Examples: "edit 03_05", "is this value consistent across the docs?", "add a drift linter", "publish the docs to the wiki", "where does the Lorenz constant live?"

2026-07-1819

memory-maintenance

Alexey-Lukin/silken_net

Use when curating the persistent file-based memory (…/memory/MEMORY.md + per-fact *.md) — structuring/grouping the index, removing cruft or duplication, fixing stale index hooks, trimming a bloated index line, or ensuring open action-items in memory are also tracked in 00_07. The HOW lives in .claude/prompts/memory_housekeeping.md; the memory FORMAT standard lives in the system prompt (don't restate). Iron rule: NO AMNESIA — preserve wins over cleanup. Examples: "почисти память", "поструктуруй memory", "повидаляй дублі в памяті", "memory housekeeping", "чи всі to-do з памяті є в 00_07?"

2026-07-1819

picogk

Alexey-Lukin/silken_net

Use when working on the silken_net Code-as-CAD surface — PicoGK voxel/SDF geometry generation in tools/cad/ (the Ti-coin in-vitro coupon, the Zone-1 gyroid anode, the CartesianGyroid SDF, future PEEK Radome) and the CEM (Computational Engineering Model) manifests that drive them. Knows the non-obvious gotchas — render lattices via `new Voxels(IImplicit, BBox3)` + BoolIntersect NOT voxBounding.voxIntersectImplicit (uncatchable native OpenVDB abort at fine voxel on thin bored parts), headless `Library.Go(voxel, task, bEndAppWithTask:true)` not the stale v1.6 `new Library()`, ImplicitRadialGyroid axis-singularity → cartesian gyroid, dimensionless gyroid wallParam + voxel-dependent porosity (MEASURE it), the voxel-resolution floor, ImplicitUsings-ENABLED for vendored LEAP source — and the local-verify discipline (`dotnet run -- verify` → metrics.json, exit 0/1). Routes to 01_02 §6 (PicoGK stack + Noyron methodology) + 01_01 §5 (anchor geometry) + tools/cad/README, does not restate. Examples: "generate the gyroid

2026-07-1819

name

telemetry-pipeline

description

Telemetry Pipeline

SSOT Documents — Read These First

Document	What it covers
`CLAUDE.md §1`	Proof of Growth pipeline — full A→D flow (sense→…→mint SCC)
`CLAUDE.md §5`	Sidekiq strict-priority queues + Lorenz/StatusByte + AES invariants
`CLAUDE.md §6`	Telemetry cross-domain gotchas (oracle_status prefix · KENOSIS · partitions)
`docs/05_02_Proof_of_Growth_Pipeline.md`	Exact worker ordering with queue assignments
`docs/05_03_Tokenomics_SCC_and_SFC.md`	Growth points, SCC minting (slashing → `05_05`)
`docs/03_05_Hardware_Symmetric_Crypto_and_Security.md §3`	AES decrypt chain, key management

Gotchas Not Obvious From Docs

DID 0x00000000 in a batch is DEAD (ARCH.54, 2026-07-03) — the old Queen-Sentinel pseudo-tree is dropped on BOTH paths (ECB and CCM): the pulse rides the SIGNED QATT-v2 envelope header (8B health block, firmware/common/queen_attest.h) → UnpackTelemetryWorker#enqueue_envelope_health → GatewayTelemetryWorker. Never re-add gateway metrics as a fake tree — it eats a CIFO slot, breaks the CCM stride, and health without a valid Ed25519 must not exist (masking-attack). Canon: 03_02 §7 + 06_08 §1.3.
oracle_status prefix — call log.oracle_status_fulfilled? not log.oracle_status == "fulfilled". String-backed enum with oracle_status_ prefix.
Dual computation — server Lorenz (Float) must match firmware mruby (Float). Was BigDecimal before FW.7 — old to_d code is a bug now.
Queue drain is strict — uplink (#1) drains COMPLETELY before alerts (#2). Telemetry flood blocks alerts. By design.
Validations removed from TelemetryLog — KENOSIS TITAN. Check is in TelemetryUnpackerService.valid_sensor_data?. Don't add validations back to model.
Partition-aware lookups — TelemetryLog RANGE-partitioned by created_at. Always use find_with_partition_pruning(id, created_at).
«Wire = вхід GP» contract (E.63 (г), wire-rev2.1) — the CCM frame carries BOTH dT fields: raw (bytes 12..13, diagnostics/server-EMA) and ema_delta_t_s (bytes 20..21) = the EXACT number metabolic_health consumed on the device → check_metabolic_divergence! recomputes GP statelessly via Attractor.expected_homeostasis_gp(ema) (byte-identical mirror of bio_contract.rb §4.3 — edit the formula/thresholds THERE first, mirror second, regen lorenz_bytecode.h). The branch is observational (warn+metric) until the bench calibrates DELTA_T_FAST_S/DELTA_T_SLOW_S; ema_delta_t_s is transient (stripped pre-persist, like lorenz_temperature_c/device_z). ECB frames carry no ema → branch honestly skips. Canon: 03_04 §4.3 + 03_01 §13.6.
firmware_version_id = wire-ЗВІТ, не FK (SEC.20, 2026-07-12) — post-SEC.20 семантика [semantic:1|reverted:1|contract_id&0x3FFF] (дзеркало firmware/common/fw_report.h): читай через TelemetryLog#firmware_report_semantic?/reverted?/contract_id (id ПО МОДУЛЮ 14 біт — НЕ join і не пряме порівняння з BioContractFirmware.id); legacy-кадри (без semantic-біта) несуть C-image константу — contract-версії НЕ мають. reverted? → EwsAlert firmware_reverted (термінальний: re-issue лише версією > спаленої — 03_06 §4 bump-інваріант).
TelemetryLog тепер несе MRV-lineage сліди (ARCH.12/E.60, 2026-07-19) — mint-інтенти отримують детерміновані вікна вимірів (Wallet watermark-курсор → telemetry_window_* на tx), а pin-воркер стемпить telemetry_logs.{archive_root, merkle_leaf} (E.60 Фаза 1б). Перший AR-колбек моделі: before_update seal-guard — мутація z_value/bio_status/created_at/tree_id стемпнутого рядка = raise (KENOSIS недоторканий: intake = insert_all, колбек не стріляє; oracle_status/verified_by_iotex — не leaf-поля, вільні). Leaf-формула One-Home = 05_02 §E.60 (Mrv::TelemetryLeaf, LEAF_VERSION). Не додавай у leaf-payload нове поле без LEAF_VERSION-bump.
Device-event 0x57 = ОКРЕМИЙ L1-канал, не телеметрія (SEC.21, 2026-07-12) — рідкісні security-події (canary-trip) НЕ їдуть телеметрійним трактом: окремий CoAP PUT device/event/<uid> → DeviceEventWorker (не UnpackTelemetryWorker). Королева підписує cleartext-конверт власним EDSK (тег SLKN-QEVT1, окремий від QATT2) → worker verify gateway-origin (HardwareKey.ed25519_public_key_hex, як QATT-батч), Rails LoRa-ключа НЕ торкається. Не плутай з CCM blind-courier телеметрії (там per-DID decrypt на Rails); тут — L1-підпис Королеви. Trust L1-observational, НІКОЛИ не money-path. Дім 03_05 §2.2а + 03_02 §7а.

Common Tasks

Add telemetry field: firmware pack → TelemetryUnpackerService unpack → DB migration → Phlex dashboard component → update docs/05_02
Change minting logic: BlockchainMintingService → the 2-guard oracle chain (IoTeX + oracle_status) protects PATH 1 only (latent — ARCH.53 §🗄️: dispatch = local marker, DON-callback unwired, closure refused 2026-07-19); KYC (Hadron) guards ALL paths and is the sole PATH-2 perimeter (live PATH 2 mint = optimistic, KYC-only; L0-custodial + ex-post clawback). Service-home = 04_02 §4; tokenomics course → 05_03 (see web3-pipeline skill)