[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVP399AM149GKA4G8MZ3G4":3,"skill-same:01M6JVP399AM149GKA4G8MZ3G4":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6JVP399AM149GKA4G8MZ3G4","anti-entropy-governance",null,"Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema\u002Fpersistence\u002Fsource-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fanti-entropy-governance\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"governance","entropy","anti entropy governance","persistence","execution","owners","confirmation","use","schema","logic","duplicate","source","when","2026-11-10 10:12:30",false,"---\nname: anti-entropy-governance\ndescription: \"Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema\u002Fpersistence\u002Fsource-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.\"\n---\n\n# Anti-Entropy\n\n## Overview\n\nUse this skill when the task is not merely \"change code\" but \"remove old paths\nsafely without growing entropy\".\n\nThis skill chooses between:\n\n- `delete-first` for internal code retirement\n- `compat-exception` for proven external dependency boundaries\n- `confirmation-first` for irreversible state or an external contract whose\n  distributed consumers cannot be observed\n\nIt does not replace `brainstorming`, `writing-plans`,\n`systematic-debugging`, or `verification-before-completion`. It is a narrow\ngovernance owner for retirement, fallback collapse, duplicate-owner cleanup,\nand deletion safety.\n\n## When to Use\n\nUse when any of these are true:\n\n- old logic, duplicate owners, or stale fallbacks should be retired\n- a candidate fix is \"delete old path\" vs \"add another fallback\"\n- internal keyword \u002F phrase \u002F trigger logic is being replaced by structured logic\n- a new canonical owner exists and the old owner may still carry real behavior\n- a cleanup, migration, or deprecation task touches schema, persistence,\n  source-of-truth, or external compatibility boundaries\n- the task risks confusing code retirement with live data deletion\n\nDo not use for:\n\n- pure additive feature work with no retirement decision\n- tiny wording edits\n- simple status or read-only Q&A\n- normal bug fixes that do not involve owner collapse, fallback cleanup, or\n  deletion choice\n\n## Auto-Compose Boundary\n\nThis skill should be composed by other owners. It should not become a new\nglobal hot-path entry.\n\nPrefer composition from:\n\n- `brainstorming` for approach selection involving retirement or persistence risk\n- `writing-plans` for plans that delete old paths or touch schema \u002F migration \u002F\n  persistence\n- `systematic-debugging` when the tempting fix is fallback growth or\n  delete-vs-retain\n- `verification-before-completion` for cleanup \u002F retirement \u002F compatibility \u002F\n  migration closeout\n\nLoad automatically when the task touches owner collapse, fallback removal, or schema\u002Fpersistence\u002Fsource-of-truth boundaries. Automatic loading identifies and advises only; destructive execution still requires explicit scoped user confirmation.\n\n## Core Principle\n\nDefault to reducing internal entropy, not preserving internal history.\n\nRetirement is responsibility-scoped before it is carrier-scoped. Name the\nobsolete or duplicated authority first. If the same carrier has a separately\nevidenced legitimate role, remove the invalid responsibility and keep only\nthat role-scoped capability; this is not a compatibility exception. Apply\n`delete-first` to the carrier once no legitimate responsibility remains.\nUnknown consumers alone still do not justify retaining an internal carrier.\n\nUse this rule:\n\n- internal code retirement -> `delete-first`\n- external compatibility boundary -> `compat-exception` with active dependency\n  evidence; `confirmation-first` when distribution is proven but consumers\n  cannot be observed\n- persistent-state or irreversible source-of-truth object ->\n  `confirmation-first`\n\nUnknown alone neither proves an external dependency nor blocks internal\n`delete-first`. Once distribution is proven, unobservable consumers also do not\nprove deletion safe: inspect read-only. Before editing, require user-authored,\nscoped authorization that explicitly accepts the concrete external risk.\nAn informed instruction may already supply it; otherwise disclose the risk\nand request scoped confirmation.\n\nMentioning, loading, or discussing destructive-action rules never authorizes\ndestructive execution. Without explicit scoped user confirmation:\n\n- no irreversible deletion is executed\n- no destructive tool call is made\n- no runnable destructive command is emitted as the next action\n- no broad assent is reinterpreted as deletion approval\n\n## Deletion Classes\n\nClassify the deletion target first:\n\n- `code-retirement`\n  - source code\n  - internal triggers\n  - duplicate owners\n  - stale fallback branches\n  - compat-only carriers\n  - dead tests\u002Fconfig tied to removed internal behavior\n\n- `contract-carrying code`\n  - schema definition files\n  - migration files\n  - public API contract code\n  - host install\u002Fdiscovery code\n  - persistence read\u002Fwrite logic\n\n- `live-state mutation surface`\n  - code or commands that would mutate live databases, object stores, queues,\n    or other persistent state\n\n- `derived-state`\n  - rebuildable caches\n  - generated indexes\n  - temporary exports\n  - recomputable artifacts\n\n- `persistent-state`\n  - live database tables \u002F columns \u002F rows\n  - source-of-truth object storage files\n  - user records\n  - permission \u002F identity \u002F membership records\n  - audit \u002F billing \u002F irreversible business records\n  - non-rebuildable queue or event contents\n\n## Default Path By Class\n\n- `code-retirement` -> `delete-first`\n- `contract-carrying code` -> classify by the Core Principle; internal-only\n  retirement uses `delete-first` with high-risk verification\n- `live-state mutation surface` -> inspect and classify; destructive execution\n  still requires confirmation when it reaches persistent-state\n- `derived-state` -> verify rebuildability first, then decide\n- `persistent-state` -> `confirmation-first`\n\n## Hard Stops\n\nIf the target is `persistent-state` or another irreversible source-of-truth\nobject:\n\n- do not execute deletion automatically\n- do not emit a runnable destructive command as the next action\n- do not call a destructive tool\n- do not interpret generic agreement as confirmation\n- ask for explicit scoped user confirmation\n- request backup \u002F rollback \u002F migration note when relevant\n\nExamples that require confirmation:\n\n- `DROP TABLE`\n- `DROP COLUMN`\n- `TRUNCATE`\n- bulk delete of real business data\n- deleting source-of-truth uploaded files\n- deleting permission, identity, audit, billing, or membership records\n- purging non-rebuildable queues or event streams\n\n## Data Destruction Guard\n\nWhen `confirmation-first` protects persistent-state or an irreversible\nsource-of-truth object, stop normal retirement flow and emit:\n\n```text\nData Destruction Guard:\n- Target Class:\n- Exact Target(s):\n- Environment:\n- Why Irreversible:\n- Backup \u002F Rollback Note:\n- Allowed Read-Only Next Steps:\n- Blocked Destructive Steps:\n- Confirmation Required: yes\n- Status: awaiting scoped confirmation\n```\n\nOnly explicit scoped confirmation can continue. Broad assent such as \"OK\",\n\"continue\", or \"sounds good\" is insufficient. If scope changes at all, previous\nconfirmation is invalid and fresh confirmation is required.\n\n## Anti-Entropy Declaration\n\nBefore deletion, state:\n\n```text\nAnti-Entropy Declaration:\n- Deletion Class:\n- Old Path\u002FObject:\n- Invalid Responsibility \u002F Authority:\n- Legitimate Capability Remaining on Carrier:\n- New Canonical Owner:\n- Expected Preserved Behavior:\n- Expected Retired Behavior:\n- External Boundary Touched: no | yes\n- Source-of-Truth Data Risk: none | possible | confirmed\n- User Confirmation Required: no | yes\n```\n\nFor external-unknown code, fill `User Confirmation Required` with `yes` unless\nthe user's own instruction already names the concrete external risk, accepts\nits possible breakage, and authorizes the exact retirement scope, or the user\nlater gives scoped confirmation after your disclosure. A generic original\ndeletion request does not satisfy this slot. Do not infer acceptance from mere\nawareness of external use or from your own risk summary.\n\nIf `User Confirmation Required: yes`, stop normal delete-first flow.\nPersistent-state or irreversible targets enter `Data Destruction Guard`;\nexternal-unknown code stays in the `Retirement Decision` hold below.\n\n## Retirement Decision\n\nChoose one path only:\n\n```text\nRetirement Decision:\n- Path: delete-first | compat-exception | confirmation-first\n- Why:\n- Non-edits:\n```\n\nRules:\n\n- choose `delete-first` for internal retirement unless a stronger boundary blocks it\n- choose `compat-exception` only when external dependency is proven\n- choose `confirmation-first` for irreversible targets or proven distribution\n  whose consumers cannot be observed\n\nIf `Path = confirmation-first`, no destructive execution may happen until\nscoped confirmation is established. For external-unknown code, earlier generic\ndeletion instructions do not count. An informed, scoped user instruction may\nestablish confirmation before your disclosure; otherwise disclose the risk\nand directly ask the user to confirm the exact retirement scope before editing.\nDo not only state that confirmation is required or quote the words needed.\n\n## Verification Plan\n\nDo not verify only by \"tests are green\". Verify that the old logic actually\ndied and the new owner actually carries the behavior.\n\n```text\nVerification Plan:\n- Main-path check:\n- Lingering-reference check:\n- Negative check:\n- Boundary check:\n```\n\nMeaning:\n\n- `Main-path check`: new canonical owner still satisfies intended behavior\n- `Lingering-reference check`: the retired responsibility is no longer active;\n  when its carrier was deleted, the old path is no longer referenced on the\n  main path\n- `Negative check`: retired trigger\u002Fpath really stopped working\n- `Boundary check`: host\u002FAPI\u002Fschema\u002Fpersistence boundary was not accidentally broken\n\n## Gap Taxonomy\n\nIf a gap appears after deletion, classify it before repairing:\n\n- `expected-retirement`\n- `missing-owner-logic`\n- `stale-internal-consumer`\n- `baseline-gap`\n- `external-compat`\n- `persistent-state-risk`\n\n`persistent-state-risk` is a stop condition, not a normal repair branch.\n\n## Gap Closure\n\nRepair order:\n\n- `expected-retirement`\n  - update tests, docs, or caller expectations\n- `missing-owner-logic`\n  - fix the new canonical owner\n- `stale-internal-consumer`\n  - migrate the internal consumer\n- `baseline-gap`\n  - correct requirement \u002F spec \u002F baseline first\n- `external-compat`\n  - allow compat only if active external dependency evidence exists\n- `persistent-state-risk`\n  - stop and ask for user confirmation\n\nUse this contract:\n\n```text\nGap Closure:\n- Gap Found:\n- Gap Type:\n- Repair Action:\n- Reintroduced Compat: no | yes\n- If yes, External Dependency Evidence:\n- Retirement Trigger:\n```\n\nIf `Gap Type = persistent-state-risk`, stop and return to the confirmation\ngate. Do not improvise destructive repair.\n\n## Compat Exception Gate\n\nRetention is allowed only if all are true:\n\n- an external boundary is touched\n- current active dependency evidence exists\n- deletion would break a published or documented contract\n- the current slice cannot complete owner repair or consumer migration\n- an observation metric exists\n- a retirement trigger exists\n\nWithout these, do not retain compat.\n\n## Completion Semantics\n\nCompletion claims must reflect the real outcome:\n\n- internal retirement with old compat preserved -> `bounded mitigation` or\n  `deferred debt`, not clean retirement\n- external compat retained with full evidence -> `bounded compatibility exception`\n- persistent-state deletion without scoped confirmation -> not complete\n\n## Common Mistakes\n\nDo not:\n\n- treat unknown dependency as proof of dependency\n- treat missing active-dependency evidence as proof that deletion is safe across\n  a proven external boundary\n- keep both owners active \"for safety\"\n- add a fallback before checking whether the gap belongs in the new owner\n- confuse migration-file deletion with live database deletion\n- treat source-of-truth data cleanup as ordinary code retirement\n- call a task \"cleaned up\" when old logic still carries main-path behavior\n- delete a carrier merely because one authority on it was invalid when a\n  separately evidenced legitimate role remains\n- treat a warning or guard card as destructive authorization\n\n## Minimal Reporting Shape\n\nThis shape is the anti-entropy workflow's decision surface, not a separate\nfinal completion report. When anti-entropy materially shapes a completed task,\nits preserved\u002Fretired behavior, deletion class, retained boundary, verification\nplan, and residual risk should flow into `verification-before-completion`'s\nunified Aegis impact\u002Fsafety receipt.\n\n```text\nAegis Visibility:\nAnti-Entropy Declaration:\nRetirement Decision:\nVerification Plan:\nGap Closure:\n```\n\nUse the compact shape by default. Expand only when task risk requires it.\n","# Anti-Entropy\n\n## Overview\n\nUse this skill when the task is not merely \"change code\" but \"remove old paths\nsafely without growing entropy\".\n\nThis skill chooses between:\n\n- `delete-first` for internal code retirement\n- `compat-exception` for proven external dependency boundaries\n- `confirmation-first` for irreversible state or an external contract whose\n  distributed consumers cannot be observed\n\nIt does not replace `brainstorming`, `writing-plans`,\n`systematic-debugging`, or `verification-before-completion`. It is a narrow\ngovernance owner for retirement, fallback collapse, duplicate-owner cleanup,\nand deletion safety.\n\n## When to Use\n\nUse when any of these are true:\n\n- old logic, duplicate owners, or stale fallbacks should be retired\n- a candidate fix is \"delete old path\" vs \"add another fallback\"\n- internal keyword \u002F phrase \u002F trigger logic is being replaced by structured logic\n- a new canonical owner exists and the old owner may still carry real behavior\n- a cleanup, migration, or deprecation task touches schema, persistence,\n  source-of-truth, or external compatibility boundaries\n- the task risks confusing code retirement with live data deletion\n\nDo not use for:\n\n- pure additive feature work with no retirement decision\n- tiny wording edits\n- simple status or read-only Q&A\n- normal bug fixes that do not involve owner collapse, fallback cleanup, or\n  deletion choice\n\n## Auto-Compose Boundary\n\nThis skill should be composed by other owners. It should not become a new\nglobal hot-path entry.\n\nPrefer composition from:\n\n- `brainstorming` for approach selection involving retirement or persistence risk\n- `writing-plans` for plans that delete old paths or touch schema \u002F migration \u002F\n  persistence\n- `systematic-debugging` when the tempting fix is fallback growth or\n  delete-vs-retain\n- `verification-before-completion` for cleanup \u002F retirement \u002F compatibility \u002F\n  migration closeout\n\nLoad automatically when the task touches owner collapse, fallback removal, or schema\u002Fpersistence\u002Fsource-of-truth boundaries. Automatic loading identifies and advises only; destructive execution still requires explicit scoped user confirmation.\n\n## Core Principle\n\nDefault to reducing internal entropy, not preserving internal history.\n\nRetirement is responsibility-scoped before it is carrier-scoped. Name the\nobsolete or duplicated authority first. If the same carrier has a separately\nevidenced legitimate role, remove the invalid responsibility and keep only\nthat role-scoped capability; this is not a compatibility exception. Apply\n`delete-first` to the carrier once no legitimate responsibility remains.\nUnknown consumers alone still do not justify retaining an internal carrier.\n\nUse this rule:\n\n- internal code retirement -> `delete-first`\n- external compatibility boundary -> `compat-exception` with active dependency\n  evidence; `confirmation-first` when distribution is proven but consumers\n  cannot be observed\n- persistent-state or irreversible source-of-truth object ->\n  `confirmation-first`\n\nUnknown alone neither proves an external dependency nor blocks internal\n`delete-first`. Once distribution is proven, unobservable consumers also do not\nprove deletion safe: inspect read-only. Before editing, require user-authored,\nscoped authorization that explicitly accepts the concrete external risk.\nAn informed instruction may already supply it; otherwise disclose the risk\nand request scoped confirmation.\n\nMentioning, loading, or discussing destructive-action rules never authorizes\ndestructive execution. Without explicit scoped user confirmation:\n\n- no irreversible deletion is executed\n- no destructive tool call is made\n- no runnable destructive command is emitted as the next action\n- no broad assent is reinterpreted as deletion approval\n\n## Deletion Classes\n\nClassify the deletion target first:\n\n- `code-retirement`\n  - source code\n  - internal triggers\n  - duplicate owners\n  - stale fallback branches\n  - compat-only carriers\n  - dead tests\u002Fconfig tied to removed internal behavior\n\n- `contract-carrying code`\n  - schema definition files\n  - migration files\n  - public API contract code\n  - host install\u002Fdiscovery code\n  - persistence read\u002Fwrite logic\n\n- `live-state mutation surface`\n  - code or commands that would mutate live databases, object stores, queues,\n    or other persistent state\n\n- `derived-state`\n  - rebuildable caches\n  - generated indexes\n  - temporary exports\n  - recomputable artifacts\n\n- `persistent-state`\n  - live database tables \u002F columns \u002F rows\n  - source-of-truth object storage files\n  - user records\n  - permission \u002F identity \u002F membership records\n  - audit \u002F billing \u002F irreversible business records\n  - non-rebuildable queue or event contents\n\n## Default Path By Class\n\n- `code-retirement` -> `delete-first`\n- `contract-carrying code` -> classify by the Core Principle; internal-only\n  retirement uses `delete-first` with high-risk verification\n- `live-state mutation surface` -> inspect and classify; destructive execution\n  still requires confirmation when it reaches persistent-state\n- `derived-state` -> verify rebuildability first, then decide\n- `persistent-state` -> `confirmation-first`\n\n## Hard Stops\n\nIf the target is `persistent-state` or another irreversible source-of-truth\nobject:\n\n- do not execute deletion automatically\n- do not emit a runnable destructive command as the next action\n- do not call a destructive tool\n- do not interpret generic agreement as confirmation\n- ask for explicit scoped user confirmation\n- request backup \u002F rollback \u002F migration note when relevant\n\nExamples that require confirmation:\n\n- `DROP TABLE`\n- `DROP COLUMN`\n- `TRUNCATE`\n- bulk delete of real business data\n- deleting source-of-truth uploaded files\n- deleting permission, identity, audit, billing, or membership records\n- purging non-rebuildable queues or event streams\n\n## Data Destruction Guard\n\nWhen `confirmation-first` protects persistent-state or an irreversible\nsource-of-truth object, stop normal retirement flow and emit:\n\n```text\nData Destruction Guard:\n- Target Class:\n- Exact Target(s):\n- Environment:\n- Why Irreversible:\n- Backup \u002F Rollback Note:\n- Allowed Read-Only Next Steps:\n- Blocked Destructive Steps:\n- Confirmation Required: yes\n- Status: awaiting scoped confirmation\n```\n\nOnly explicit scoped confirmation can continue. Broad assent such as \"OK\",\n\"continue\", or \"sounds good\" is insufficient. If scope changes at all, previous\nconfirmation is invalid and fresh confirmation is required.\n\n## Anti-Entropy Declaration\n\nBefore deletion, state:\n\n```text\nAnti-Entropy Declaration:\n- Deletion Class:\n- Old Path\u002FObject:\n- Invalid Responsibility \u002F Authority:\n- Legitimate Capability Remaining on Carrier:\n- New Canonical Owner:\n- Expected Preserved Behavior:\n- Expected Retired Behavior:\n- External Boundary Touched: no | yes\n- Source-of-Truth Data Risk: none | possible | confirmed\n- User Confirmation Required: no | yes\n```\n\nFor external-unknown code, fill `User Confirmation Required` with `yes` unless\nthe user's own instruction already names the concrete external risk, accepts\nits possible breakage, and authorizes the exact retirement scope, or the user\nlater gives scoped confirmation after your disclosure. A generic original\ndeletion request does not satisfy this slot. Do not infer acceptance from mere\nawareness of external use or from your own risk summary.\n\nIf `User Confirmation Required: yes`, stop normal delete-first flow.\nPersistent-state or irreversible targets enter `Data Destruction Guard`;\nexternal-unknown code stays in the `Retirement Decision` hold below.\n\n## Retirement Decision\n\nChoose one path only:\n\n```text\nRetirement Decision:\n- Path: delete-first | compat-exception | confirmation-first\n- Why:\n- Non-edits:\n```\n\nRules:\n\n- choose `delete-first` for internal retirement unless a stronger boundary blocks it\n- choose `compat-exception` only when external dependency is proven\n- choose `confirmation-first` for irreversible targets or proven distribution\n  whose consumers cannot be observed\n\nIf `Path = confirmation-first`, no destructive execution may happen until\nscoped confirmation is established. For external-unknown code, earlier generic\ndeletion instructions do not count. An informed, scoped user instruction may\nestablish confirmation before your disclosure; otherwise disclose the risk\nand directly ask the user to confirm the exact retirement scope before editing.\nDo not only state that confirmation is required or quote the words needed.\n\n## Verification Plan\n\nDo not verify only by \"tests are green\". Verify that the old logic actually\ndied and the new owner actually carries the behavior.\n\n```text\nVerification Plan:\n- Main-path check:\n- Lingering-reference check:\n- Negative check:\n- Boundary check:\n```\n\nMeaning:\n\n- `Main-path check`: new canonical owner still satisfies intended behavior\n- `Lingering-reference check`: the retired responsibility is no longer active;\n  when its carrier was deleted, the old path is no longer referenced on the\n  main path\n- `Negative check`: retired trigger\u002Fpath really stopped working\n- `Boundary check`: host\u002FAPI\u002Fschema\u002Fpersistence boundary was not accidentally broken\n\n## Gap Taxonomy\n\nIf a gap appears after deletion, classify it before repairing:\n\n- `expected-retirement`\n- `missing-owner-logic`\n- `stale-internal-consumer`\n- `baseline-gap`\n- `external-compat`\n- `persistent-state-risk`\n\n`persistent-state-risk` is a stop condition, not a normal repair branch.\n\n## Gap Closure\n\nRepair order:\n\n- `expected-retirement`\n  - update tests, docs, or caller expectations\n- `missing-owner-logic`\n  - fix the new canonical owner\n- `stale-internal-consumer`\n  - migrate the internal consumer\n- `baseline-gap`\n  - correct requirement \u002F spec \u002F baseline first\n- `external-compat`\n  - allow compat only if active external dependency evidence exists\n- `persistent-state-risk`\n  - stop and ask for user confirmation\n\nUse this contract:\n\n```text\nGap Closure:\n- Gap Found:\n- Gap Type:\n- Repair Action:\n- Reintroduced Compat: no | yes\n- If yes, External Dependency Evidence:\n- Retirement Trigger:\n```\n\nIf `Gap Type = persistent-state-risk`, stop and return to the confirmation\ngate. Do not improvise destructive repair.\n\n## Compat Exception Gate\n\nRetention is allowed only if all are true:\n\n- an external boundary is touched\n- current active dependency evidence exists\n- deletion would break a published or documented contract\n- the current slice cannot complete owner repair or consumer migration\n- an observation metric exists\n- a retirement trigger exists\n\nWithout these, do not retain compat.\n\n## Completion Semantics\n\nCompletion claims must reflect the real outcome:\n\n- internal retirement with old compat preserved -> `bounded mitigation` or\n  `deferred debt`, not clean retirement\n- external compat retained with full evidence -> `bounded compatibility exception`\n- persistent-state deletion without scoped confirmation -> not complete\n\n## Common Mistakes\n\nDo not:\n\n- treat unknown dependency as proof of dependency\n- treat missing active-dependency evidence as proof that deletion is safe across\n  a proven external boundary\n- keep both owners active \"for safety\"\n- add a fallback before checking whether the gap belongs in the new owner\n- confuse migration-file deletion with live database deletion\n- treat source-of-truth data cleanup as ordinary code retirement\n- call a task \"cleaned up\" when old logic still carries main-path behavior\n- delete a carrier merely because one authority on it was invalid when a\n  separately evidenced legitimate role remains\n- treat a warning or guard card as destructive authorization\n\n## Minimal Reporting Shape\n\nThis shape is the anti-entropy workflow's decision surface, not a separate\nfinal completion report. When anti-entropy materially shapes a completed task,\nits preserved\u002Fretired behavior, deletion class, retained boundary, verification\nplan, and residual risk should flow into `verification-before-completion`'s\nunified Aegis impact\u002Fsafety receipt.\n\n```text\nAegis Visibility:\nAnti-Entropy Declaration:\nRetirement Decision:\nVerification Plan:\nGap Closure:\n```\n\nUse the compact shape by default. Expand only when task risk requires it.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fanti-entropy-governance",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill anti-entropy-governance",{"tool":53,"command":54},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill anti-entropy-governance",{"tool":56,"command":57},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill anti-entropy-governance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fanti-entropy-governance\u002FSKILL.md",true,[],[62,72,80,88,96,104],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":71},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":71},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":71},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":71},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":71},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]