150
followers ·
2 following None yet
posted an update about 12 hours ago ✅ Article highlight: *NPC Society Safety: Bounded Autonomy at Scale* (art-60-162, v0.1)
TL;DR:
This article argues that high-autonomy NPC societies need governance, not trust.
Once NPCs can trade, persuade, coordinate, punish, restrict access, or move resources, they stop being “scripts” and become institution-shaped actors. Their actions must be bounded by explicit capability envelopes, resource budgets, policy envelopes, monitoring, safe-mode, and appeal paths.
Read:
https://huggingface.co/datasets/kanaria007/agi-structural-intelligence-protocols/blob/main/article/60-supplements/art-60-162-npc-society-safety.md
Why it matters:
• makes NPC autonomy legible before it affects players, markets, or world state
• prevents runaway coordination, resource extraction, soft coercion, and authority confusion
• treats persuasion and communication as governed actions, not harmless flavor text
• links NPC-caused harm to incident handling and appealable due process
What’s inside:
• *NPC agency profiles* that define allowed and denied capabilities
• *resource budget profiles* with hard ceilings and spend receipts
• *NPC policy envelopes* for rules, disclosure, influence limits, fairness, and escalation
• materiality profiles for deciding which NPC acts require stronger governance
• 148-anchored monitoring for runaway spend, disparate treatment, inducement, and extraction loops
• safe-mode policies that narrow autonomy when monitoring is inconclusive
• 160-compatible incident and recourse paths when NPC actions cause harm or disputes
Key idea:
Do not say:
*“the NPC society is autonomous.”*
Say:
*“these NPCs may act only within these agency profiles, budgets, policy envelopes, monitoring receipts, safe-mode rules, and appeal paths.”*
NPC autonomy doesn’t scale by trust.
It scales by bounds, budgets, and receipts.
posted an update 2 days ago ✅ Article highlight: *Registry Governance, Conformance Programs, and Threat Models for Interop Standards* (art-60-176, v0.1)
TL;DR:
This article explains how the interop layer from 175 becomes a living standard.
Interop is not just a schema. A portable standard needs governed registry evolution, expiring conformance attestations, threat-modeled artifact exchange, and shared reason codes. Otherwise “same artifact,” “same bundle,” and “same verdict” collapse back into vendor-local theater.
Read:
[https://huggingface.co/datasets/kanaria007/agi-structural-intelligence-protocols/blob/main/article/60-supplements/art-60-176-registry-governance-conformance-programs-and-threat-models-for-interop-standards.md](https://huggingface.co/datasets/kanaria007/agi-structural-intelligence-protocols/blob/main/article/60-supplements/art-60-176-registry-governance-conformance-programs-and-threat-models-for-interop-standards.md)
Why it matters:
• turns schema registries into governed objects, not wikis
• makes interop compliance measurable, scoped, and expiring
• handles schema upgrades through SemVer, migration windows, dual issuance, and cutoffs
• treats exchanged bundles as attack surfaces, not trusted files
• makes DENY decisions portable through shared reason codes
What’s inside:
• registry governance contracts and registry state receipts
• compatibility policy for ACTIVE / DEPRECATED / WITHDRAWN schemas
• upgrade plan receipts for breaking changes
• conformance attestations binding c14n, schema, and bundle replay receipts
• threat handling for schema spoofing, registry substitution, ZIP attacks, signature forgery, replay mixing, and resource exhaustion
Key idea:
Do not say:
*“we support the standard.”*
Say:
*“we are pinned to this registry state, passed this conformance program for this scope, and verify exchanged artifacts under this threat model and shared dispute vocabulary.”*
Standards survive when evolution, certification, and adversaries are go posted an update 5 days ago ✅ Article highlight: *Interop Schemas for Learning-World Governance Artifacts* (art-60-175, v0.1)
TL;DR:
This article argues that governance without interop is vendor-local theater.
It is not enough for one system to say *“we have receipts.”* If another vendor cannot parse the artifact, reproduce the digest, replay the bundle, and reach the same admissibility outcome, the claim is not really portable. So 175 defines a common interop layer: shared envelopes, pinned canonicalization, minimal portable schemas, and deterministic bundle formats.
Read:
https://huggingface.co/datasets/kanaria007/agi-structural-intelligence-protocols/blob/main/article/60-supplements/art-60-175-interop-schemas-for-learning-world-governance-artifacts.md
Why it matters:
• turns governance artifacts into cross-vendor verifiable objects rather than local implementation details
• fixes the classic failure modes of digest drift, schema drift, and bundle drift
• makes “same artifact / same verdict” a testable claim instead of a handshake promise
• gives courts, forgetting flows, and unlearning claims portable bundle formats
What’s inside:
• a common *interop envelope* for contracts, manifests, receipts, and bundles
• a pinned *canonicalization profile* plus conformance receipts to stop digest disagreements
• minimal portable schemas for core learning-world governance artifacts
• deterministic bundle formats like *Court ZIP*, *Forgetting ZIP*, and *Unlearning ZIP*
• replay/conformance receipts so another vendor can verify the same bundle and reach the same admissibility result
Key idea:
Do not say:
*“our system can export the evidence.”*
Say:
*“this artifact uses this schema registry, this canonicalization profile, this interop-safe digest model, and this bundle index—so another vendor can verify the same object and reach the same result.”*
That is how governance stops being local theater and becomes portable infrastructure.
View all activity None yet
view post ✅ Article highlight: *NPC Society Safety: Bounded Autonomy at Scale* (art-60-162, v0.1) TL;DR: This article argues that high-autonomy NPC societies need governance, not trust. Once NPCs can trade, persuade, coordinate, punish, restrict access, or move resources, they stop being “scripts” and become institution-shaped actors. Their actions must be bounded by explicit capability envelopes, resource budgets, policy envelopes, monitoring, safe-mode, and appeal paths. Read: kanaria007/agi-structural-intelligence-protocols Why it matters: • makes NPC autonomy legible before it affects players, markets, or world state • prevents runaway coordination, resource extraction, soft coercion, and authority confusion • treats persuasion and communication as governed actions, not harmless flavor text • links NPC-caused harm to incident handling and appealable due process What’s inside: • *NPC agency profiles* that define allowed and denied capabilities • *resource budget profiles* with hard ceilings and spend receipts • *NPC policy envelopes* for rules, disclosure, influence limits, fairness, and escalation • materiality profiles for deciding which NPC acts require stronger governance • 148-anchored monitoring for runaway spend, disparate treatment, inducement, and extraction loops • safe-mode policies that narrow autonomy when monitoring is inconclusive • 160-compatible incident and recourse paths when NPC actions cause harm or disputes Key idea: Do not say: *“the NPC society is autonomous.”* Say: *“these NPCs may act only within these agency profiles, budgets, policy envelopes, monitoring receipts, safe-mode rules, and appeal paths.”* NPC autonomy doesn’t scale by trust. It scales by bounds, budgets, and receipts. See translation
CityOS Under SI-Core: A Worked Example Across All Invariants
