organon-absorb

Files (1)

• SKILL.md

SKILL.md (first lines)

# Organon Absorb

1. Resolve the philosophy using [the resolution contract](../../OrganonCore/skills/references/philosophy-resolution.md). Run `node <AgentOrganon>/scripts/resolve.js --cwd <calling-directory>` with `--philosophy <path>` when explicitly supplied. Locate `<AgentOrganon>` from this skill's directory; preserve the caller's directory for resolution.
2. If resolution fails, stop. For missing default candidates, suggest `organon-philosophy init`; an invalid explicit path must be corrected, not replaced by a default or Core.
3. Read the selected `core_version` and compare it with `organon.coreVersion` in [package.json](../../package.json). Surface the resolver's source-version warning when outside the range. If metadata cannot be read, report the version as unknown and retain the selected text as the assessment baseline; managed writes still require valid supported metadata. These warnings are not philosophical validity judgments.
4. Delegate the request to [organon-core-absorb](../../OrganonCore/skills/organon-core-absorb/SKILL.md), passing the resolved philosophy path as the fixed adopted baseline, with its real source directory. Identify any intended adoption target from the request and caller context; pass any established target and the allowed actions without substituting the baseline for a different target. Resolve relative target paths from the caller's directory. A request to revise the caller's own adopted text may use the same path for both roles. For an advisory request without an established target, keep the target unspecified and continue the authorized review; resolution alone does not select a write destination. Keep a proposed replacement and Core method constraints distinct. Apply Core's required independent review and concrete user decision before adoption. Reading a Core symlink as the baseline does not select Core as the adoption target; an actual request to revise protected Core text requires its explicit maintenance or absorption workflow, not a management write or symlink bypass.

From shendeguize/AgentOrganon, MIT.

More from shendeguize/AgentOrganon