APIS
Stable system interfaces
Public interfaces should be versioned, documented and predictable enough that developers can build without reverse-engineering core system behaviour.
SAGE / DEVELOPERS
A future application platform built around stable interfaces and clear expectations.
Sage does not currently publish a production SDK, public API contract or final application-distribution model. This page defines the developer-platform direction and the standards Vidran intends to meet before external developers are asked to depend on it.
TOOLING
Development workflow
Future tooling should make it clear how applications are created, tested, packaged, debugged and prepared for supported Sage environments.
DISTRIBUTION
Trustworthy software delivery
Application distribution should balance developer access, user security, provenance and a practical path for independent software.
CURRENT STATUS
No public SDK announced
Vidran will not publish placeholder API references, invented command-line tools or speculative SDK requirements simply to make the platform appear mature. Developer documentation should follow working interfaces.
DEVELOPER PRINCIPLES
What external developers should eventually be able to expect.
Versioned interfaces
Changes should be communicated and compatibility expectations made explicit.
Useful documentation
Examples, reference material and platform behaviour should reflect software developers can actually run.
Clear permissions
Applications should understand what system access they have and what requires user approval.
Feedback path
External developers need a route to report platform issues, documentation gaps and compatibility problems.
DEVELOPER INTEREST