Task Matrix for AI Agents

Before making a change, use this matrix to identify the binding sources, permitted scope, and acceptance criteria.

Validate the human rule and machine contract together

The JSON Schema v1 defines the required fields. The versioned contract above is the complete valid example.

Valid

{
  "product": "dbxapp",
  "version": "4.5.3",
  "contract": "ai-task-boundaries",
  "tasks": { "system_module_source": { ... } }
}

Version, priority, sequence, tasks, and change-log rules are present.

Invalid

{
  "product": "dbxapp",
  "tasks": { "system_module_source": {
    "forbidden": []
  } }
}

The version, contract name, sequence, and mandatory boundaries are missing.

Validator: php dbx/modules/dbxDocs/tests/dbxDocsAiContract_test.php checks the schema contract, version, required task types, and database-driver boundary.

Classify the task first

Task	Required sources	Allowed scope	Prohibited	Minimum acceptance
Menu / customer content	AGENTS.md, affected installation, menu template	named installation only	product source, version change, update package	desktop, mobile, states, links
System or module source	AGENTS.md, SOURCE-CONVENTIONS.md, module manual, affected DD/FD	development source and affected module	customer data, parallel framework, direct database driver	syntax, contracts, focused tests, SelfTest
Design	design contract, existing tokens and templates	selected design or released bundle	inline special paths, core copies, unrelated designs	light/dark, responsive, focus, contrast
CMS / documentation	documentation standard, audience page, canonical source	CMS and documentation installation	duplicate sources, unversioned claims, local public paths	metadata, TOC, links, search, HTTP 200
Data model	dbxDB, DD, FD, module manual, sync path	complete DD/FD and controlled synchronization	PDO, mysqli, SQLite3, native drivers, unconfirmed data transfer	dbxDB/DD contract, sync, round trip, rollback
Release / update	update contract, VERSION, manifest, release notes	completed release only	premature versioning, private myX, docs as product update	upgrade, integrity, rollback, SelfTest

Binding agent sequence

Classify: identify customer content, system source, documentation, or release.
Read: read every required source completely.
Scope: record target paths and explicit exclusions.
Change: reuse existing contracts and framework components.
Verify: run minimum acceptance plus risk-based regressions.
Log: after success, write exactly one change-log entry for the logical block.
Report: state the outcome, tests, limits, and stored change_log data.

Priority and validity

Explicit user instructions come first, followed by installation-level AGENTS.md rules, this task contract, and the technical guides. The JSON contract always carries the public dbxapp version.