Experts are the domain authorities who define how professional workflows execute on Majormatic. You do not write code. You define logic, accept professional responsibility, and earn when your tools are used.
An Expert is a domain authority who defines how a workflow should be executed. Experts are solicitors, accountants, compliance officers, researchers, and other professionals who understand the logic behind high-stakes work — not software engineers who write backend code.
Majormatic operates as a two-sided governed execution ecosystem. Experts define the logic. Users execute the workflows. The platform Kernel enforces the rules and records everything.
Defines execution tools (ABI Apps) using Builder. Accepts the Digital Oath. Publishes to Appstream.
Governs execution. Enforces rules. Routes to engines. Validates outputs. Records audit trail.
Selects an app. Provides inputs. Reviews the draft output. Acknowledges and finalises.
Experts occupy a distinct accountability position in this chain. The platform executes correctly — it does not make judgements about whether the logic is right. That responsibility rests entirely with the Expert who authored the app.
Experts build Execution Tools — structured apps that professional users invoke to run governed workflows. Each app is an ABI (Application Binary Interface) contract: a set of static JSON files that declare the structure, constraints, and domain logic of the tool.
Experts use Builder to design their app — a visual tool that generates the required ABI files. No manual JSON editing is required in Builder.
Specify what data the user must provide: documents, IDs, parameters, options, and references. Each input field must have a clear label, type, and validation rule.
Specify the ordered steps the system must perform: Parse → Analyse → Validate → Format. Each step must have clear input and output. No hidden logic.
Specify the exact structure of the final result. Outputs must be structured, consistent, and explainable. Ambiguous or open-ended output schemas are rejected during review.
Specify when human review is required. For legal decisions, financial calculations, and regulatory outputs, supervision_required must be set to true in governance.json.
Run test cases, validate edge cases, accept the Digital Oath, and submit to Appstream. Once published, your app is available to professional users and generates revenue on use.
Experts operate within a clear accountability boundary. The platform is responsible for execution correctness — that outputs conform to declared schemas, that governance rules are enforced, and that audit trails are complete. Experts are responsible for logic correctness — that the workflow actually produces accurate, professional-grade results.
Your position in Appstream is determined by your app's performance, not by promotional spending or platform favours. The ranking algorithm rewards accuracy, user trust, and execution reliability.
What the Digital Oath means, when you take it, and why responsibility acceptance is structural to the platform
Read guide →How to use Builder to design workflows, configure inputs, define outputs, and validate logic
View guide →Mandatory test library structure, test types, edge case coverage, and quality standards for published apps
View standards →How Builder generates the 6 ABI files: input.json, preset.json, result.json, meta.json, governance.json, info.json
View guide →Step-by-step walkthrough of building, testing, and submitting your app to Appstream
Read guide →Answers to common questions about the Expert role, Digital Oath, performance, and revenue
View FAQ →Design your first execution tool and bring your domain expertise to governed professional workflows.