polyrepo-boundaries

Files (2)

• SKILL.md
• index.md

SKILL.md (first lines)

# Polyrepo boundaries

Each sibling under the workspace root is an independent Git repository with its own history, release, CI, and
governance. Pushing Xberg does not publish a sibling dependency.

## Ownership

- `xberg`: reusable Rust document-intelligence primitives, public Rust API, CLI/server surfaces, bindings, and Xberg
  CI/release packaging.
- `xberg-enterprise`: product and deployment behavior that consumes Xberg. Check it before removing or reshaping Rust
  primitives, even when the symbol is not exposed in language bindings.
- `alef`: binding, documentation, snippet, and e2e generation defects. Work around a generator defect in Xberg only
  when necessary; report and fix the reusable cause in Alef.
- `liter-llm`: reusable LLM client behavior, provider request construction, endpoint validation, and network-security
  controls owned by that client.
- `crawlberg`: crawling, URL retrieval, and crawler-specific network policy. Put SSRF protection at the component that
  performs the outbound request; callers may add stricter policy but cannot replace the transport boundary.
- `sceptre`: reusable Sceptre OCR models/runtime. Xberg owns its adapter, configuration, and integration behavior.

## API placement

Keep reusable primitives in the Rust crate when enterprise or Rust callers need them. Bindings should expose a
primitive only when it forms a coherent supported language API; Rust-only public functionality does not need an FFI
wrapper. Compatibility and deprecation policy applies to public APIs, not private internals.

For a cross-repo fix, identify the lowest owning layer, coordinate the dependency/release order, and verify each
repository independently. Commit and publish the dependency before updating a consumer to a version that contains the
fix.

From xberg-io/xberg, MIT.

More from xberg-io/xberg