Visit REZICS

Developers

Open source, with standalone packages.

Services, website, account pages, design documents, and API definitions live in one public repository. The platform uses AGPL-3.0. The Wiki toolkit and document format package use Apache-2.0 and do not depend on REZICS services.

View the source

Licenses

Two licenses

  • AGPL-3.0

    The platform: services, website, account pages, and documentation.

    services/ · apps/ · generated/ · docs/

  • Apache-2.0

    Standalone packages: @rezics/wiki-toolkit and @rezics/document. No REZICS account required.

    packages/wiki-toolkit/ · packages/document/

Repository

What is in the repository

  • services/

    Backend services. Main provides the API and MCP server. Account handles sign-in and OAuth authorization.

    AGPL-3.0

  • apps/web/

    The REZICS website. Like your code, it gets data only through the API.

    AGPL-3.0

  • apps/web/zones/official/

    Presentation code for official Zones, with one package per directory.

    AGPL-3.0

  • apps/accounts/

    Account pages for sign-in, security, and connected apps.

    AGPL-3.0

  • packages/wiki-toolkit/

    Local Wiki toolkit, its protocol, and its skill.

    Apache-2.0

  • packages/document/

    REZICS document format, with text and blocks defined in a JSON schema.

    Apache-2.0

  • generated/openapi/

    OpenAPI documentation generated from route declarations.

    AGPL-3.0

  • docs/

    Design decisions, contracts, and operating procedures with their reasons.

    AGPL-3.0

Run

Run it on your computer

Install the pinned toolchain and container runtime. Three commands start the API, account service, website, and account pages, then show their URLs.

task toolchain:install
task dev
task urls
From the repository documentation.
import {
  fromPlainText, parseDocument,
  serializeDocument,
} from '@rezics/document';

const snapshot = fromPlainText(
  'Chinese characters\nSecond paragraph',
);
parseDocument(snapshot);
const stored =
  serializeDocument(snapshot);
@rezics/document does not require a REZICS account, service, or database. Excerpt from its documentation.

Put rules in code, and reasons in the docs.

Express rules as code when types, tests, or checks can enforce them. Document why a decision was made, with its date and rationale.

Developers

More pages

Build your tools on one API.

Use your own code to read and write works, library entries, and community data. Every operation follows REZICS identity and authorization rules.

Visit REZICS

Products

Modules

Language