[OMEGA-346] Add optional Telos goal-representation module (lib_telos_goals.metta)

[arielagor]

What

Adds lib_telos_goals.metta — an optional, opt-in goal-representation module for OmegaClaw — plus a short usage doc. Additive only; no changes to the core.

Why

OmegaClaw is goal-autonomous, but the public core has no dedicated, inspectable model of what the goals are — run.metta and lib_omegaclaw.metta contain no goal token. Goal misunderstanding (pursuing the literal request while missing the real goal; serving one person while externalising cost onto the group; chasing an abandoned goal) is where an autonomous agent is most dangerous, and it is rarely represented or measured.

What's in it

• A small goal graph in OmegaClaw's idiom: (goal id scope owner status) + (rel type src dst) atoms.
• Parameterized derivation rules: conflicts, collective goals, goals-of-owner, blocked-on-dependency, individual↔collective alignment, and a combined telos-reading.
• Side-effect-free on load (no queries run at import); opt-in via !(import! &self (library OmegaClaw-Core lib_telos_goals)).

Verified

Loads on the standalone Hyperon interpreter and in a live OmegaClaw (PeTTa) runtime — the conflict rule derives (conflict-between alice-train dao-fair-access) inside the running agent's AtomSpace.

Measuring it

Paired with a 14-scenario / 7-category goal-understanding benchmark that can score OmegaClaw or any agent: https://github.com/arielagor/telos (MIT, same licence). Contributed from the BGI Sprint I project "Telos".

Happy to adjust naming/placement to fit your conventions.

🤖 Disclosure: authored with Claude Code — Telos is an openly AI-built submission under human oversight.

[arielagor]

Quick verification context for reviewers:

• Runs in OmegaClaw's own MeTTa engine, not just Hyperon. I ran the module's named rules through sh run.sh in singularitynet/omegaclaw:latest (PeTTa / SWI-Prolog). They derive:

  (conflict-between alice-train dao-fair-access)   ; telos-conflicts
  (collective-goal dao-fair-access dao)            ; telos-collective-goals
  (blocked dao-fair-access on gpu-quota)           ; telos-blocked  (nested match + if)
  

  Full transcript: https://github.com/arielagor/telos/blob/main/results/omegaclaw-metta-load.log
• Test coverage (so it can't regress): https://github.com/arielagor/telos/blob/main/tests/test_metta.py exercises each named rule on Hyperon, including the nested telos-blocked.
• Additive only, side-effect-free on load. Happy to move the file, rename, or add an Autotests/ entry if that fits your conventions better.

[timur-ashkenov]

@arielagor Looks good to me overall - I like that this is additive, opt-in, and side-effect-free on load.
Left a few comments below, none of these are blockers.

[timur-ashkenov]

telos-reading is described as a “full goal reading,” but it seems to only cover the cross-goal/global view - achieved goals aren’t included because telos-achieved requires parameters.

Is that intentional? If so, maybe the naming/docs could make that clearer. Otherwise, would it make sense to add an all-achieved-goals view here?

[timur-ashkenov]

Could you clarify the intended integration here? The module defines the representation and queries, but OmegaClaw doesn’t currently infer or assert goal / rel atoms on its own.

[timur-ashkenov]

subsumes is part of the public schema, but no current rule uses it and its direction is not documented. Is it intentionally reserved for future use?