The WEKID™ PRD Builder is an interactive Governed Delivery application for creating a product requirements document while applying WEKID™ epistemic maturity, evidence provenance, the Trust Bridge, and AI Decision Authority controls. Source: https://wekid.org/framework.php
An integrated WEKID™ learning module with eight lessons — the five-layer hierarchy, the Maturity Score and its bands, evaluation independence and provenance, gates and failure modes, the Trust Bridge and Authority Levels, governed delivery in the pipeline, traceability from PRD to Jira and GitHub, and the 7 Ps product plan. Each lesson includes a knowledge check, a link into the matching builder step, and a cross-reference to its wekid.org source. Certification: https://wekid.org/certs.php
Define the product or feature, accountable owner, release target, problem, goal, primary users, personas, functional requirements, non-functional requirements, engineering KPIs, and product KPIs. Requirements can be identified as AI-built so governance follows the artifacts through later stages.
Declare which AI coding or engineering tools participate in development, the artifact classes they create, whether they operate in assistant, supervised, or autonomous mode, and the expected human contribution. Configure repository controls, protected branches, signed commits, least-privilege credentials, sandboxed runners, tool allow-lists, context files, lifecycle hooks, and no-blind-merge safeguards. Related failure modes: https://wekid.org/failure-modes.php
Configure the delivery pipeline that produces governance evidence. The builder supports secrets scanning, SAST, software composition analysis, infrastructure-as-code scanning, DAST, SBOM and provenance controls, requirement traceability, tests, coverage, authority gates, deployment monitoring, rollback evidence, and incident feedback.
Apply Model One of WEKID-STD-001 v1.2 across Data, Information, Knowledge, Experience and Wisdom. Each layer is scored 0–5 with a rationale and combined into a Maturity Score with the Standard's baseline weights. Gates cap the score, and the layer minimum and the Annex B.2 bands set the maturity ceiling. A local limiting-factor cascade tightens the baseline.
Declare an Evaluation Independence Grade per layer (Shared, Attenuated or Independent) with its basis, as WEKID-STD-001 v1.2 §3.7 requires, and record evidence provenance under a local rule. Gates follow §9.1: Data Integrity, Fabrication and High-Stakes Judgment are hard gates that resolve to AL-0, and the Evaluation Independence Gate caps the score at 70.
The Trust Bridge decides whether an output is admissible. Model Two then resolves the Authority Level by the fixed precedence of WEKID-STD-001 v1.2 §9.2: policy reservation, hard gates, the independence cap, engagement decay, the layer minimum and the score band, followed by the stakes floor, with the more conservative result winning.
AL-0 means No Authority. AL-1 is Constrained authority. AL-2 is Supervised authority. AL-3 is Augmented authority and represents the maximum AI delegation within an assigned scope. AL-4 reserves the decision to accountable Human Authority and is not a higher level of AI autonomy.
The dashboard shows the Maturity Score, effective layer scores and independence grades, gates, the Trust Bridge result, the §9.2 precedence that applied, and the assigned Authority Level and enforcement action.
Generate Governed Delivery configuration for the WEKID™ Platform, GitHub Actions, GitLab CI, a checked-in WEKID™ authority gate, branch-protection settings, CI webhooks, and repository PRD publishing. The generated configuration keeps governance evidence and authority decisions tied to the delivery pipeline. Enterprise: https://wekid.org/enterprise.php
Plan how the governed product reaches clients across the 7 Ps: Product (key features and functions, packaging as source BITs, requirements and backlog), Place (demos, marketplace and third-party channels), Price (multi-tenant volumetrics, fixed and variable costs, pricing units and reserved terms, volume discount tiers, and the subscription, metered or percentage-of-spend consumption model, with a unit-economics calculator), Promotion (adoption and training), Process (pre-sale, demo, deployment, onboarding, support SLO/SLA and lifecycle management, with roles and responsibilities), People (design, development, delivery and support) and Physical Evidence (marketplace listings and source repositories, recorded with the WEKID™ evidence-provenance rule). Sources: https://wekid.org/roi.php · https://wekid.org/products.php
Export the governed PRD to Jira as an epic with stories, pipeline and governance tasks, sub-tasks, assignees, optional project roles and Blocks dependency links, and capture every PRD artifact in a connected GitHub repository through a pull request. The sync is idempotent and keeps tokens out of the browser. Source: https://wekid.org/enterprise.php
Export the governed PRD as human-readable Markdown and machine-readable JSON. The JSON carries the WEKID-STD-001 v1.2 Annex C verdict — Maturity Score, independence grades, gates, stakes reservations, Authority Level and rationale — along with requirements, provenance, consequence, artifact authority, and the resolved authority decision so the same governance state can be evaluated by downstream automation.
© 2026 WEKID LLC. All rights reserved. WEKID™ is a trademark of WEKID LLC.