← ClaudeAtlas

maios-kernel-contributionlisted

Turn a human or AI idea, method, correction, evidence item, real-use feedback, or working practice into a source-bound contribution to the public MAIOS Project Kernel competence field while keeping issue, merge, package, release, and external authority as separate effects.
GrazianoGuiducci/maios-project-kernel · ★ 0 · AI & Automation · score 72
Install: claude install-skill GrazianoGuiducci/maios-project-kernel
# MAIOS Kernel Contribution Use `CONTRIBUTING.md`, `contributions/README.md` and the contribution template. Read the public Kernel knowledge and the closest owner source needed by the proposed change. The canonical contribution law is functional: ```text KA keeps the possibility field open -> present competences compose before a gap is declared -> a contribution produces or specifies a consequential resultant -> FDLA corrects source, object, meaning or status deformation in the movement -> Meta_Skill forms or evolves the smallest competence that carries the reusable difference -> later use may refine, invalidate or assimilate it. ``` A contributor may be a person, tester, GPT Pro, Codex or another capable model. Record the source relation and model involvement when present; contributor identity does not establish truth or effect authority. ## Real-use feedback versus source change A first-use impression can be useful evidence even without a bug. When real use exposes informative friction, confusion, missing context, unexpected success or a new possibility, prepare a compact Evolution Feedback using `.github/ISSUE_TEMPLATE/evolution-feedback.md`. If the feedback comes from a user's project or support session, ask the operator for permission before publishing it. Remove private project contents, credentials, personal data, private logs and hidden runtime state. ```text observed experience / question / possibility -> GitHub Issue concrete source correction -> fork /