The Digital Oath

Before publishing any execution tool to Appstream, every Expert must explicitly accept professional responsibility for that version. This is not a checkbox. It is a structural accountability mechanism.

"I accept professional responsibility for this execution tool version."

This statement is presented to the Expert immediately before each publication or version update. Without explicit acceptance, the app cannot be published.

What Accepting the Oath Means

When you accept the Digital Oath, you are making a formal professional declaration. The platform records the acceptance against your identity, the app version, and the timestamp. This record is permanent and forms part of the app's audit chain.

1

You stand behind the logic

You affirm that the workflow you have designed is accurate, complete, and appropriate for its declared professional purpose. You have reviewed the logic and believe it produces correct outputs.

2

You accept accountability for outcomes

If the logic is wrong, the platform will execute it correctly — producing wrong results. The Expert, not the platform, is accountable for logic-level errors in published apps.

3

You confirm supervision is correctly set

For high-risk outputs — legal decisions, financial calculations, regulatory documents — supervision_required must be set to true. Accepting the oath confirms you have evaluated the supervision requirements correctly.

4

You commit to maintaining the version

Publishing a version signals that it is production-ready. If issues are discovered after publication, you are responsible for releasing a corrected version promptly and notifying platform governance.

When the Oath Applies

The Digital Oath is required for every version publication event — not just the first. Each time you update an app and submit a new version, you must accept the oath for that specific version.

v1.0
Initial publication — Oath accepted for the first published version. The app enters Appstream and becomes available to users.
v1.1
Minor update — Even small changes require a new oath. Each version is an independent accountability event. The oath is not inherited from prior versions.
v2.0
Major revision — The previous version remains accessible in the audit history. The new version carries its own oath acceptance and forms a new audit baseline.
Important: Old versions are never overwritten. Each version and its corresponding oath acceptance remain in the audit record permanently.

Responsibility in Practice

The distinction between Expert responsibility and platform responsibility is precise. Understanding this boundary is essential before accepting the oath.

Area
Expert Responsibility
Platform Responsibility
Logic correctness
Expert owns this
Platform does not verify logic meaning
Schema validation
Expert declares the schema
Platform enforces it on every run
Supervision setting
Expert sets supervision_required
Platform enforces the supervision gate
Output accuracy
Expert's logic determines accuracy
Platform validates structure, not meaning
Execution infrastructure
Expert has no access
Platform owns all execution
Security enforcement
Expert has no security role
Platform enforces all security controls

What You Must Never Do

Accepting the Digital Oath creates specific obligations. Violations undermine the trust architecture of the platform and may result in app suspension or removal from Appstream.

✗
Accept the oath for logic you have not verified. The oath is not a formality. Do not accept it without genuinely reviewing your workflow for accuracy and completeness.
✗
Skip supervision for high-risk outputs. If your app produces legal decisions, financial calculations, or regulatory outputs, supervision_required must be true. Setting it to false to reduce friction is a policy violation.
✗
Overclaim accuracy in the app description. Describing your app as producing certified, authoritative, or definitive outputs when it produces drafts subject to professional review is misleading and prohibited.
✗
Ignore post-publication quality signals. If users are consistently modifying your outputs or execution failures are increasing, this indicates a logic problem. You are responsible for investigating and releasing a fix.

Expert Documentation

Expert Overview

What the Expert role is, what you build, and how you fit into the Majormatic platform

Read overview →

Testing & Quality

How to build a test library and validate your logic before accepting the oath

View guide →

Builder Guide

Step-by-step walkthrough of designing your app and the full publication process

Read guide →

Ready to Build?

Start with the Builder guide to design your first execution tool.

Builder Guide Testing Guide