How the deterministic decisions are made

The tools apply published categorical rules in a fixed order. They do not call a generative model, inspect task text, rank vendors, or let a score override a safety boundary.

AI Task Fit Check

Task Fit methodology task-fit-1.0.2 answers five questions: whether AI should influence the task, the least complex suitable pattern, maximum autonomy, controls required before use, and the evidence, review, stop, and escalation instructions.

Decision order

1. Validate required answers and reject impossible combinations.
2. Collect every rule finding activated by those answers.
3. Apply exclusions from the broadest boundary to the narrowest pattern.
4. Apply the most restrictive autonomy ceiling.
5. Combine and de-duplicate every required control.
6. Select the least complex remaining solution pattern.
7. Calculate explanatory fit and inherent-risk bands.
8. Select the disposition.
9. Assemble the rationale and the appropriate pilot or next-safe-step, evaluation, review, stop, and escalation instructions.

Exclusions, unavailable controls, and autonomy ceilings take precedence. Benefit, volume, and explanatory scores cannot override them.

What rule findings can do

Exclusion

Prohibits the requested workflow, one or more patterns, or all AI influence.

Required control

Permits the workflow only when a named safeguard is active before use.

Autonomy ceiling

Limits the most consequential action AI may take.

Warning

Adds explanation without changing the decision by itself.

Four dispositions

• Proceed: a pattern is available without an additional task-specific control or a lower autonomy ceiling.
• Proceed with controls: the same task boundary remains valid, but named safeguards or lower autonomy are mandatory.
• Redesign: the requested workflow is blocked. No pattern is recommended, the current workflow must not be piloted, and the materially changed task must be assessed again.
• Do not use AI: AI must not perform, draft, rank, summarize, recommend for, or otherwise influence the current task.

Risk and autonomy definitions

The risk band describes the task before controls. This version does not calculate residual risk, and controls do not lower the displayed band.

• Low: minor, visible, and reversible errors.
• Medium: material rework, confusion, cost, or limited external impact.
• High: material effects on people, money, rights, operations, or reputation.
• Critical: severe or irreversible harm, or improper influence over a high-impact decision.

The autonomy ceiling can allow, from least to most influence:

1. No AI influence
2. Draft for human review
3. Recommend to a responsible person
4. Decide with required approval
5. Take a bounded, reversible action

Pattern selection

The engine selects the least complex pattern that can satisfy the task's evidence, control, and action requirements: human-only, conventional software, direct prompt, prompt with supplied context, retrieval-grounded workflow, bounded tool workflow, or bounded agent. More autonomy or technical complexity is rejected when a simpler pattern is sufficient.

Product-policy boundaries

Version 1 contains two explicit Use AI Clearly house-policy hard stops: material employment screening or selection, and operational assistance intended to steal credentials or account access. These are conservative product rules, not a complete statement of the law. Selecting “neither” does not mean a task is legally, professionally, or organizationally permitted.

The check relies entirely on the reader's categorical answers. It does not inspect the actual workflow, evidence, people, systems, policies, or jurisdiction. Input and result schema version is 1.0.0. Review examples calculated by the current engine.

Output Verification Builder

Methodology output-verification-1.0.0 creates an acceptance and review plan from categorical task requirements. It determines:

• whether a review checklist can be generated, requires elevated review, or is blocked;
• sample or full review coverage;
• the minimum reviewer level;
• required checks, evidence, approvals, and stop conditions; and
• capability or use-boundary blockers that cannot be overridden.

The builder does not receive or evaluate an actual output. It cannot certify correctness, authorize a high-impact decision, or authorize automatic external action. It uses input and result schema version1.0.0.

Representative checklists show the ready, elevated-review, and blocked boundaries.

Review and validation status

VMCSoft Digital has owner-reviewed and approved the methodology, fixtures, implementation alignment, and current editorial release. Automated rule and fixture tests verify deterministic behavior. Independent domain review and moderated target-user validation have not been completed, so the site does not claim either.

Owner approval is not legal, medical, financial, employment, regulatory, or safety approval. See theeditorial review record andreport a safety or methodology concern.

See the public changelog for release and methodology history.