Add interdependent cross-repository work graph - #46
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 40a114387c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "repositories": [ | ||
| { | ||
| "repository": "owner/name", | ||
| "commit": "<40-hex commit>", |
There was a problem hiding this comment.
For stack-level runs where a corpus, package, schema, workflow, or publication surface changes the answer, this reference manifest can only encode Git repositories with 40-hex commits. Those participants either have to be omitted from the hashed graph identity or mis-modeled as repositories, so later agents cannot reproduce the complete graph for non-repo evidence sources; add typed participants with digest/version/schema fields or parallel artifact/schema sections before this becomes the machine contract.
Useful? React with 👍 / 👎.
| "repository": "owner/name", | ||
| "commit": "<40-hex commit>", | ||
| "authority": "what this participant may define", | ||
| "relation": "how it participates in this work" |
There was a problem hiding this comment.
When a manifest has multiple producers or consumers, this per-participant relation text cannot identify which participant depends on which other participant, so two different work graphs can share the same participants and boundaries while still getting the same work_graph_sha256. That undermines the validation and materialization order the skill requires; include a hashed edge list such as from, to, and relation_type for producer, consumer, schema, or corpus links.
Useful? React with 👍 / 👎.
Resolves index-file conflicts between the domain-claims skill (PR #45, merged) and the interdependent-work-graph skill (this PR): AGENTS.md, CLAUDE.md, and README.md procedural-skill enumerations now carry both skills. Also reflows one line in domain-claims/SKILL.md so the phrase "ordinary language remains fluid" is contiguous, repairing the test_domain_claims_skill assertion that has been failing on main since PR #45 merged. Full local validation: 95 unit tests, skill-lib drift, skill compliance, ratios --strict, llms-build --check, and RepoLOTO all pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MpVzs74WPmx5tWSrmik3wM
Responds to the four automated review findings on the 1.0.0 reference contract without invalidating the manifests already sealed by the EDCM OEWN 2025 workflows: - state explicitly that repositories array order is part of the hashed identity in 1.0.0 (key sorting does not reorder arrays); - state that certification-status and empirical-validity non-transfer remain binding skill obligations even though 1.0.0 carries no explicit fields, and that those fields ride the next schema revision; - document how non-repository participants are encoded in 1.0.0; - record the expected next-revision items (explicit certification/empirical fields, canonical ordering, typed participants, hashed edge list) as visible hmmm. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MpVzs74WPmx5tWSrmik3wM
3 participants
Purpose
Make cross-repository coordination a reusable organization skill rather than a repo-local habit.
Core rule
The skill loads when a task spans or changes the contract between multiple repositories, when exact producer/evidence identities must travel together, or when an agent is about to reduce a stack-level problem to one repository workspace.
Contract
hmmmidentities;hmmm.Reference schema
Introduces
the-interdependency.stack-manifestversion1.0.0, with a deterministic SHA-256 work-graph identity over exact participants and boundaries.Originating implementation
EDCM PR #25 is using this shape for the OEWN 2025 run across EDCM, METAPAT, UCNS, skill-lib, and Open English WordNet.
Remaining work in this PR
hmmm
The organization-wide persistent service or UI for live work graphs is not yet selected. Content identity is not yet cryptographic producer authentication.