[FScholPer]

Summary

First step of the Agent Context Attention Layer for Eclipse S-CORE. Turns this repo into an APM monorepo-hybrid and lands Phase 0 only: the schema / data model. No adapters, graph composition, ranking, apm.yml generation, or MCP server implementation yet — those are later phases; placeholders mark where they go.

(Supersedes #2, which auto-closed when the branch was renamed.)

The layer's job is to turn "trace everything" across S-CORE's 80+ repos into "surface what matters for my current context". Everything becomes a typed, provenance-bearing graph node/edge; later phases rank them per (task, repo, role) and project the top-N into a generated APM package that compiles to AGENTS.md and every other harness.

Layout — APM monorepo-hybrid

mcp-servers/
  apm.yml                     # root marketplace manifest + local-path packages
  apm-policy.yml              # starter (tighten-only) org/company policy
  libs/
    score-context/            # shared, MCP-free Python ENGINE + Phase 0 schema
      src/score_context/schema/{nodes,edges,provenance}.py, context.jsonld
      src/score_context/delta.py
  packages/
    _template/                # copy-to-add-a-package skeleton (.apm/<type>/ dirs)
    context/                  # the attention layer AS an APM package
      apm.yml                 #   targets: copilot/claude/codex/cursor/gemini/opencode
      .apm/context/           #   generated attention output lands here (Phase 1+)
      .apm/skills/query-context/SKILL.md   # WIP stub

Adding an APM package = copy packages/_template, edit its apm.yml, drop primitives under .apm/<type>/. MCP servers are declarations under a package's dependencies.mcp: — not a separate directory. The engine is a shared lib in libs/, not fused into the package.

Schema (the substance)

Design principle: sphinx-needs is one signal source, not the foundation. Node vocabulary is split into two families:

• Needs-model nodes — IDs reused verbatim from score_metamodel.yaml (stkh_req, feat_req, comp_req, feat, comp, mod, logical interfaces, dec_rec, safety/security analysis types, testcase, …). Not forked.
• Trace/event nodes — the part deliberately outside the needs model, where most context change actually happens: issue, discussion, pull_request, commit, code_change, contract, repo, module, team, person, artifact, ci_result.

Edge relations are a superset: all needs_extra_links from the metamodel plus the ADR trace relations (affects, depends_on, discussed_in, blocks, supersedes, conflicts_with, authored_by, owns), with ADR_RELATION_MAPPINGS documenting the overlaps.

Invariants baked in now so adapters can't violate them later:

• Natural keys only — need id / dec_rec id / org/repo#123 / commit sha / file path / bazel module label. No synthetic UUIDs.
• Provenance mandatory on every node AND edge — {repo, sha?, adapter, confidence∈[0,1], observed_at}.
• pydantic v2, extra="forbid" throughout.

context-delta — the one unit every future adapter emits

class ContextDelta:            # delta.py
    signal: Signal             # {type, source: SourceRef, provenance, weight, decays}
    graph_ops: list[GraphOp]   # discriminated union: UpsertNode | UpsertEdge

context.jsonld maps every node/edge type to a stable IRI under https://eclipse-score.github.io/context-attention/ns#.

Repo baseline & CI

Eclipse governance files added (modeled on eclipse-score/module_template, adapted to a uv/APM repo — no Bazel/sphinx scaffolding): LICENSES/Apache-2.0.txt + REUSE.toml (REUSE-compliant, reuse lint clean, 29/29 files), .github/CODEOWNERS, .github/dependabot.yml (github-actions/pip/pre-commit), CONTRIBUTION.md, .pre-commit-config.yaml (ruff + reuse).

First CI workflow .github/workflows/on-pr.yml:

• reuses eclipse-score/cicd-workflows/.github/workflows/score-pr-checks.yml (pinned to 93aac16 / v0.0.2; skips Bazel-module check gracefully since there's no MODULE.bazel);
• a local python-checks job running uv sync + ruff + pyright + pytest.
  All third-party actions/workflows are pinned to commit SHAs.

Verification

• Python: uv sync, uv run ruff check ., ruff format --check, uv run pyright (0 errors), uv run pytest (4 passed) — all green.
• APM CLI 0.26.0: apm pack --offline returns ok:true for the root marketplace, packages/context, and packages/_template; apm marketplace check --offline → all entries OK; apm doctor marketplace/version-alignment/duplicate-name checks pass. Generated output (.claude-plugin/, .github/, apm.lock.yaml, …) is gitignored, not committed.

• Assisted by copilot

Frank Scholter Peres frank.scholter_peres@mercedes-benz.com, Mercedes-Benz Tech Innovation GmbH
Provider Information