ipadp: define L1 conformance metadata (specs/metadata.json)

[satwareAG-ironMike]

Summary

Define IPADP (Inter-Project Agentic Development Process) L1 conformance metadata for this project. This enables AI agents to discover this project's dependencies and coordinate across the satware AG multi-repo ecosystem.

Background

IPADP is satware AG's internal RFC defining how AI agents coordinate development across interlinked repositories spanning 3 Git forges (GitHub public, GitLab private, Gitea private). Each project needs a specs/metadata.json that documents its dependency graph.

RFC location: ~/internal/wiki/specs/rfc-interproject-agentic-development.md

Conformance levels:

• L1: specs/metadata.json with upstream links (structured dependency graph)
• L2: + Privacy validation passing (safe cross-repo communication)
• L3: + Automated sync triggers + morning protocol (full ecosystem coordination)

This issue targets L1 (metadata only).

Templates

Two reference implementations exist:

1. vault.satware.ai (leaf role, Gitea): ~/internal/vault.satware.ai/specs/metadata.json - standalone service, infrastructure dependencies only
2. satis (gluepoint role, GitLab): ~/internal/satis/specs/metadata.json - sits between upstream data model and downstream plugins

5-Step Process

1. Determine IPADP role:

   • leaf - consumes infrastructure/upstream but no other project depends on it
   • gluepoint - sits between upstream and downstream, translates interfaces
   • root - top of dependency tree, many downstream

2. Choose conformance level: L1 (metadata only), L2 (+ privacy CI), L3 (+ sync triggers)

3. Map upstream dependencies: What does this project depend on? (repos, Docker images, infrastructure)

4. Map downstream consumers: Who depends on this project? (code-level, not just operational)

5. Write specs/metadata.json: Document the dependency graph in the IPADP JSON schema

Acceptance Criteria

• specs/metadata.json exists with valid JSON
• schema_version is "1.0"
• name matches the project identifier
• sdd_source is "https://github.com/satwareAG/spec-kit"
• forge is correct (github / gitlab / gitea)
• visibility is correct (public / private)
• local_path follows convention (~/external/ for GitHub, ~/internal/ for GitLab/Gitea)
• ipadp.conformance_level is "L1"
• ipadp.role is determined (leaf / gluepoint / root)
• upstream section lists all repo-level dependencies with forge + local_path + role
• downstream section lists all consumers
• privacy section documents any public-to-private link concerns (forbidden by IPADP)
• AGENTS.md Child DOX Index updated to include specs/ with IPADP metadata note
• Committed and pushed

References

• IPADP RFC: ~/internal/wiki/specs/rfc-interproject-agentic-development.md
• IPADP skill: ~/.config/opencode/skills/ipadp/SKILL.md
• Rule: rules/ecosystem.ipadp.md
• Template (leaf): ~/internal/vault.satware.ai/specs/metadata.json
• Template (gluepoint): ~/internal/satis/specs/metadata.json