For developers
1 min read
This documentation specifically focuses on the developers - the bank's engineers or the delivery team's forward-deployed engineers who extend Remy: a new skill, a new monitor, a new topic page, a new source, a new page in the side panel. Everything extends on the same contracts; nothing here forks the package.
Extension work assumes a contracted Remy deployment with the developer tooling (repository, administration tool, demo installation, test suite) delivered as part of the engagement. What a bank-authored skill can reach is bounded by the connectors and permissions of its deployment.
How Remy is built
Services: One folder is one service; it owns its schema, store, command line, prose and tests. One writer per path. Dependencies point down only.
Skills: Prose task definitions that call their service's command line. Exactly one product per skill. Versioned with their service.
Contracts: A CI check for manifests, ownership, layering, imports, names, versions; build-time checks on every page.