1// PTO-UNIT: {"id":"PTO-ARCH-FEATURES-PREDICATION","surface":"arch","classification":["features","predication"],"depends_on":["PTO-ARCH-PROGRAMMING-MODEL-PREDICATE-REGISTERS"]}2// This unit owns the named architecture concept; executable state is defined by its dependencies.3
Architecture behavior
purpose scope
Purpose and scope
This unit is the named architecture concept for predication and depends on the predicate-register programming-model owner.
It provides a stable ownership and navigation point without creating a second predicate-state or execution contract.
concepts state
Concepts and visible state
The unit contains only its PTO-UNIT identity and dependency on PTO-ARCH-PROGRAMMING-MODEL-PREDICATE-REGISTERS.
Predicate register storage, indexing, reset, and reads/writes are defined by that dependency and its reachable state owners.
Instruction-specific predicate decode and no-op behavior remain with each mnemonic owner.
rules interactions
Rules and interactions
This concept introduces no ASL type, function, state variable, or transition.
A reference to predication must be resolved through the predicate-register owner and the consuming instruction's current ASL.
No default predicate sense or instruction coverage can be inferred from this marker-only unit.
boundaries
Architectural boundaries
This page cannot add missing predication semantics in explanatory prose; any new rule belongs in an owning ASL/NDF change with validation.
The named concept is portable as an identity, while concrete instruction effects stay local to their mnemonic contracts.
example usage
illustrative reading example
To decide whether a false predicate suppresses a particular instruction, read that instruction's decode and operation together with the predicate-register owner; this unit alone does not answer the question.
Use this page as the architecture index for the concept, then follow the related owner links for executable details.