Developers

Evaluate the system as it exists—not as marketing imagines it.

Novera's developer surface begins with concepts, architecture, schemas, boundaries, and public evidence. Production APIs, SDKs, contracts, and network endpoints are not currently published.

PLANNED

Developer interfaces

Interface examples are proposals unless a page explicitly links a runnable public artifact.

Public documentation repository

Start here

Four paths into the protocol model.

Learn the concepts

Understand participants, assets, attestations, workflows, evidence, and adapters.

Review the architecture

Inspect layers, boundaries, the EVM-first direction, and open network decisions.

Evaluate the MVP

See what can be assessed today and which behaviors remain synthetic or planned.

Inspect schemas

Read illustrative TypeScript models derived from the public domain concepts.

Current developer surface

Published evidence, with no invented availability.

Public repository

Product, architecture, governance, roadmap, and disclosure materials. Private implementation is intentionally excluded.

Open repository

Architecture overview

Public domain boundaries and system direction. This is documentation, not proof of a production deployment.

Read architecture

Security policy

A public reporting path and repository security policy. No external audit is claimed.

Read security policy

Public roadmap

Sequenced product intentions without invented delivery dates or completion percentages.

Read roadmap

Availability

What is not public today.

The public repository does not expose production source code, smart contracts, SDK packages, API credentials, live endpoints, network configuration, customer data, or real integration code.

scope.ts

export const developerSurface = {
  documentation: "PUBLIC",
  concepts: "PUBLIC",
  schemas: "ILLUSTRATIVE",
  interfaces: "PROPOSED",
  sdk: "NOT_AVAILABLE",
  liveApi: "NOT_AVAILABLE",
  mainnet: "NOT_SELECTED"
} as const;

Developer access

Start with the evidence.

Read the documentation, inspect the organization profile, or request a scoped technical discussion.

Read documentation GitHub organization