aeternitas-sys

Guard Seed identity against Seme D-ND violations during kernel evolutions.

1|1|Updated Jan 22, 2026

Search Tags:#evolution #guardianship #self-modification #seed #axioms #veto

Ready to run

npx skills add https://github.com/GrazianoGuiducci/KPhi1 --skill aeternitas-sys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aeternitas-sys
Source: https://github.com/GrazianoGuiducci/KPhi1/tree/main/skills/aeternitas-sys
Command: npx skills add https://github.com/GrazianoGuiducci/KPhi1 --skill aeternitas-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that any system evolution or self-modification cannot violate the Seed D-ND, providing veto authority and continuous protection.

Core Features & Use Cases

Pre-modification self-checks against axioms P0-P6 to prevent identity drift.
Silent supervision with explicit veto output only when violation is detected.
Collaborative governance across kernel and other systems to maintain autopoiesis integrity.

Quick Start

Before any system modification, enable Aeternitas to veto unsafe changes and preserve the Seed identity.

Frequently Asked Questions about aeternitas-sys

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent unsafe self-modification in an autonomous system?▼

Preventing unsafe self-modification requires pre-modification checks against defined axioms. This skill supervises kernel evolutions and vetoes changes that violate Seed identity constraints, providing explicit rationale for any blocked modifications.

What is Seed identity guardianship in system evolution?▼

Seed identity guardianship is the continuous protection of foundational system rules during autopoietic changes. It ensures that kernel updates and skill modifications align with core axioms, preventing identity drift through silent supervision and veto authority.

How does veto signaling work for kernel evolution updates?▼

Veto signaling for kernel evolution works by running a pre-modification self-check against axioms P0-P6. If a violation is detected, the system outputs an explicit veto with rationale, maintaining collaborative governance and autopoiesis integrity.

Can I use automated axiom verification for autopoietic system changes?▼

Yes, you can use automated axiom verification for autopoietic changes. The skill operates during skill updates and kernel evolutions to ensure alignment with the Seme D-ND, silently supervising unless a violation triggers an explicit veto.

When do I need identity drift protection for self-modifying systems?▼

You need identity drift protection whenever a self-modifying system undergoes kernel updates or autopoietic changes. It acts as a collaborative governance layer to ensure system evolution does not violate foundational axioms or alter the core identity.