1goal tested: Block registration lets third parties add UI without core modificationspass 0.87
- 1 task
- 2 request
- 3 response
- 4 quick read
- 5 decision
- 6 ledger
2 the request it firedrequest.yaml · hover a question
mak:goal: Block registration lets third parties add UI without core modificationsdepth: quickwhere:- src/wp-includes/blocks.php:1-100- src/wp-includes/block-editor.php:1-100ask:concerns:design:pass: "yes"1: Does `src/wp-includes/blocks.php` provide a public API to register custom blocks?2: Are custom blocks rendered through a common system rather than direct PHP output?3: Can third-party code register and enqueue block scripts without patching core?access:pass: "yes"4: Does `src/wp-includes/block-editor.php` check user capabilities before rendering blocks?5: Are block permissions enforced by role or by user capability check?6: Can an unprivileged user request a block they lack permission to see?correctness:pass: "yes"7: Are block registration inputs (name, settings) validated before storage?8: Does the block editor sanitize block attributes before rendering to HTML?9: Are server-side block renders sanitized before output?decisions:hookpoint:pass: [filter-system, factory-pattern]10:choice: How can an agent hook into block rendering without modifying registration?options: [filter-system, factory-pattern, no-hookpoint]agent-design:pass: [yes]11:choice: Is the block system architected for agents to drive UI?options: [yes, partial, no]integration-ease:pass: [easy, moderate]12:scale: How much code change is needed to add agent UI?levels: [easy, moderate, complex, redesign-needed]
3 the response that came backMM3 output, verbatim
mak:id: MM3-0001gate: failgoal: {gate: pass, p: 0.87}design: {gate: unsure, 1: 0.50, 2: 0.89, 3: 0.92}access: {gate: fail, 4: 0.06, 5: 0.35, 6: 0.44}correctness: {gate: unsure, 7: 0.42, 8: 0.42, 9: 0.34}hookpoint: {gate: pass, 10: {top: filter-system, p: 0.85}}agent-design: {gate: pass, 11: {top: "yes", p: 0.70}}integration-ease: {gate: pass, 12: {top: easy, p: 0.56}}consensus: SPLITescalate: truemdl: {recorded: none}next: mm3 template drill --parent MM3-0001 --from accessnotes: [cost estimated from tokens (no live pricing reported), "budget: $0.10 left of $0.10 · 29 of 30 runs left"]
4 quick read MM3-0001bar = p
gatefail13 questions · 1 call · 292 ms
goalpass0.87
designunsure10.5020.8930.92
accessfail40.0650.3560.44
correctnessunsure70.4280.4290.34
hookpointpass10filter-system0.85
agent-designpass11yes0.70
integration-easepass12easy0.56
5the decision it infers
Drill into access
mm3 drill digs into one weak spot, one level down, asking only about it
mm3 template drill --parent MM3-0001 --from access- the gate is FAIL: access fails; design and correctness unsure
- consensus is SPLIT and escalate is true, so do not act on this alone
6what the ledger now holds
- lineage
- run 1 of 6 in this ledger · a root run, no parent · built on later by MM3-0002
- reuse
- asked fresh: 13 questions in 1 call, ~$0.00010; every answer is kept for reuse
- recorded
- nothing from an mdl: block; the request had none
- budget
- $0.10 left of $0.10 · 29 of 30 runs left
real run jev-1.13.0 · api.typesafe.ai · 292 ms · ~$0.00010 · 13 questions · 1 call · MM3-0001 2026-09-29 WordPress @3ffb1df costs are estimates · counts include the goal question
Exact request and response text
mak:
goal: Block registration lets third parties add UI without core modifications
depth: quick
where:
- src/wp-includes/blocks.php:1-100
- src/wp-includes/block-editor.php:1-100
ask:
concerns:
design:
pass: "yes"
1: Does `src/wp-includes/blocks.php` provide a public API to register custom blocks?
2: Are custom blocks rendered through a common system rather than direct PHP output?
3: Can third-party code register and enqueue block scripts without patching core?
access:
pass: "yes"
4: Does `src/wp-includes/block-editor.php` check user capabilities before rendering blocks?
5: Are block permissions enforced by role or by user capability check?
6: Can an unprivileged user request a block they lack permission to see?
correctness:
pass: "yes"
7: Are block registration inputs (name, settings) validated before storage?
8: Does the block editor sanitize block attributes before rendering to HTML?
9: Are server-side block renders sanitized before output?
decisions:
hookpoint:
pass: [filter-system, factory-pattern]
10:
choice: How can an agent hook into block rendering without modifying registration?
options: [filter-system, factory-pattern, no-hookpoint]
agent-design:
pass: [yes]
11:
choice: Is the block system architected for agents to drive UI?
options: [yes, partial, no]
integration-ease:
pass: [easy, moderate]
12:
scale: How much code change is needed to add agent UI?
levels: [easy, moderate, complex, redesign-needed]mak:
id: MM3-0001
gate: fail
goal: {gate: pass, p: 0.87}
design: {gate: unsure, 1: 0.50, 2: 0.89, 3: 0.92}
access: {gate: fail, 4: 0.06, 5: 0.35, 6: 0.44}
correctness: {gate: unsure, 7: 0.42, 8: 0.42, 9: 0.34}
hookpoint: {gate: pass, 10: {top: filter-system, p: 0.85}}
agent-design: {gate: pass, 11: {top: "yes", p: 0.70}}
integration-ease: {gate: pass, 12: {top: easy, p: 0.56}}
consensus: SPLIT
escalate: true
mdl: {recorded: none}
next: mm3 template drill --parent MM3-0001 --from access
notes: [cost estimated from tokens (no live pricing reported), "budget: $0.10 left of $0.10 · 29 of 30 runs left"]
