Hugging Face's logo
Ikan Riddle's picture
28 2

Ikan Riddle

IkanRiddle
·

AI & ML interests

None yet

Recent Activity

reacted to kanaria007's post with 🧠 about 20 hours ago
✅ Article highlight: *Time in SI-Core* (art-60-056, v0.1) TL;DR: Most agent stacks treat time as ambient and informal: `now()` anywhere, network order as-given, logs as best effort. This article argues that SI-Core needs time as *first-class infrastructure*: separate *wall time*, *monotonic time*, and *causal/logical time*, then design ordering and replay around that so *CAS* can mean something in real systems. Read: https://huggingface.co/datasets/kanaria007/agi-structural-intelligence-protocols/blob/main/article/60-supplements/art-60-056-time-in-si-core.md Why it matters: • makes “same input, same replayed result” a system property instead of a hope • lets you prove ordering claims like *OBS before Jump* and *ETH before RML* • turns deterministic replay into a concrete contract, not “just rerun the code” • treats time/order bugs as governance bugs, not just ops noise What’s inside: • the 3-clock model: *wall / monotonic / causal* • *HLC* as a practical default timestamp backbone • minimum ordering invariants for SIR-linked traces • determinism envelopes, cassette-based dependency replay, and CAS interpretation • canonicalization, signatures, tamper-evident logs, and migration from nondeterministic stacks Key idea: If you want trustworthy replay, safe rollback, and credible postmortems, you cannot leave time implicit. You have to build clocks, ordering, and replay the same way you build security: *by design, not by hope.*
reacted to kanaria007's post with 🧠 3 days ago
✅ Article highlight: *Migrating Legacy LLM Systems to SI-Core* (art-60-055, v0.1) TL;DR: How do you migrate a legacy LLM stack without stopping delivery or rewriting everything? This article lays out a practical path: start with *OBS + SIM/SIS* for traceability, add *EVAL + PoLB* for safe change control, then split *decision (Jump)* from *effect (RML)* so autonomy becomes governable rather than ad hoc. Read: https://huggingface.co/datasets/kanaria007/agi-structural-intelligence-protocols/blob/main/article/60-supplements/art-60-055-migrating-legacy-llm-systems.md Why it matters: • turns black-box agent behavior into traceable decision/effect flows • makes prompt/tool changes governable through rollout and rollback discipline • introduces compensators and effect boundaries before incidents force them on you • gives teams a migration path without “boil the ocean” rewrites What’s inside: • a step-by-step migration sequence: *OBS + SIM/SIS → EVAL + PoLB → RML wrappers → Jump + ETH → GRP + Roles* • concrete templates for OBS bundles, EvalSurface, PoLB rollout, Jump drafts, and RML effects • anti-patterns to avoid during migration • team structure, testing strategy, readiness gates, and exit criteria for becoming “SI-native enough” Key idea: You do not migrate to SI-Core by replacing everything at once. You migrate by introducing *traceability, governed change, decision/effect separation, and replayable accountability* in that order.
reacted to kanaria007's post with 🧠 7 days ago
✅ Article highlight: *CompanionOS Under SI-Core* (art-60-053, v0.1) TL;DR: This article is *not* “CityOS for daily life.” It treats personal-scale SI as a *governance kernel + protocols + auditability layer*: what the system is, what it must guarantee, and what the user can verify. The key difference from a generic “personal AI” is simple: the human is the principal, the goals are plural and changing, and *the human must retain veto power*. CompanionOS is the runtime that makes that structurally enforceable. Read: https://huggingface.co/datasets/kanaria007/agi-structural-intelligence-protocols/blob/main/article/60-supplements/art-60-053-companion-os-under-si-core.md Why it matters: • makes personal AI accountable to the person, not to hidden service KPIs • turns cross-domain memory into something the user can govern • makes “why this jump?” structurally inspectable instead of vibe-based • treats consent as a runtime object, not a UI checkbox • keeps apps, devices, and providers visible as explicit principals/roles, not silent integrations What’s inside: • *CompanionOS* as a personal SI-Core runtime with OBS / Jump / ETH / RML + SIM/SIS + audit UI • modular personal *GoalSurfaces* for health, learning, finance, and other life domains • user override, refusal, veto, and inspectability patterns • degraded/offline mode with tighter constraints and reduced action scope • consent receipts, connector manifests, and policy bundles as exportable governance artifacts • a model of personal SI as a *kernel*, not just an app or chat wrapper Key idea: CompanionOS is not “an assistant that runs your life.” It is a *user-owned governance runtime for decisions, memory, and consent*.
View all activity

Organizations

None yet