APTA-14
AUTHORITY · JURISDICTION · ROLE · ACTIVITY · EVIDENCE · CONSEQUENCE
Determine what may apply before governance claims become execution.
This workspace does not declare legal compliance. It guides a bounded applicability review across AI governance, Environmental Integrity Governance, law, regulation, standards, codes, guidance, contracts, and TA-14 institutional routes.
RANKED AUTHORITY RESULTS
Potentially applicable instruments and supporting authorities
Federal environmental statute
Clean Air Act
The selected profile involves air emissions, atmospheric evidence, or a regulated source within the United States. Applicability depends on source classification, pollutant, jurisdiction, permit status, program delegation, and the specific implementing regulation.
01
Is the activity a stationary source, mobile source, product, fuel, or another regulated category?
02
Which pollutant, threshold, permit program, state implementation plan, or federal rule may govern?
03
Has the controlling jurisdiction adopted, delegated, or supplemented the federal requirement?
04
Which monitoring, reporting, certification, and record-retention duties apply to the actual source?
01
Source and facility identity
02
Permit and program applicability record
03
Pollutant and emission-unit inventory
04
Monitoring method and instrument record
05
Calibration and quality-assurance package
06
Emission, operating, and exception logs
07
Reporting and certification records
08
Enforcement, deviation, or corrective-action history
The statute establishes the legal framework. A determination still requires the current implementing rule, permit, jurisdiction, adopted methods, and source-specific facts.
THE TA-14 APPLICABILITY SEQUENCE
Applicability is a governed determination, not a keyword match.
Identify the real entity, facility, system, activity, product, instrument, place, and responsible role.
Classify the law, regulation, standard, code, framework, guidance, contract, or institutional architecture.
Resolve jurisdiction, market, site, affected person, receiving environment, and competent authority.
Preserve the controlling edition, effective date, amendment, adoption, permit, contract, and local modification.
Determine whether the actual role, activity, threshold, system, source, or consequence falls within scope.
Preserve the evidence required to support applicability, exemptions, exclusions, and the governed proposition.
Commit a bounded applicability finding: applicable, conditional, review required, supporting, or outside scope.
Reassess after material change, new evidence, a new version, a new jurisdiction, or a changed consequence.
GUIDED APPLICABILITY INSTITUTION
Learn the question, build the evidence, expose the uncertainty, and submit a review-ready determination package.
The applicability workspace is designed as a guided institutional pathway rather than a one-screen answer generator. Each stage teaches why the question matters, what evidence supports it, and what conditions require HOLD or escalation.
01
GUIDED DETERMINATION STAGE
Identify the governed subject
What entity, facility, system, product, activity, instrument, place, or person is being evaluated?
Applicability cannot be resolved against a vague organization-wide description. The subject must be bounded before authority can attach.
✦Legal and operating identity
✦Facility, system, product, or activity description
✦Responsible owner and accountable role
✦Location, market, and operational boundary
◆Identity is incomplete or disputed
◆The actual operating subject is not the submitted subject
◆Ownership or responsible role cannot be established
02
GUIDED DETERMINATION STAGE
Classify the activity
What is actually happening, and which legal, technical, environmental, or AI category best describes it?
Names used in marketing or internal systems do not control applicability. The real activity, source, discharge, model use, building condition, or intervention controls.
✦Process and workflow map
✦System architecture or facility process description
✦Inputs, outputs, releases, decisions, and affected parties
✦Declared use and actual use comparison
◆The activity is described only through marketing language
◆Declared use conflicts with observed use
◆Multiple activities are collapsed into one unbounded submission
03
GUIDED DETERMINATION STAGE
Resolve jurisdiction
Which geographic, sectoral, contractual, code, permit, or market authority governs the subject?
A rule may apply differently across federal, state, tribal, territorial, local, international, contractual, and adopted-code boundaries.
✦Physical and legal location
✦Market and affected-person location
✦Permit, license, contract, and code-adoption records
✦Delegation, primacy, and competent-authority records
◆Location or market is unresolved
◆Delegated authority is unclear
◆The controlling local adoption cannot be identified
04
GUIDED DETERMINATION STAGE
Resolve role and duty
Is the participant a provider, deployer, owner, operator, employer, manufacturer, generator, discharger, public authority, reviewer, laboratory, or another accountable role?
The same instrument can impose different duties on different actors. Applicability must bind the actual role to the actual obligation.
✦Organizational role and responsibility record
✦Contracts and delegation records
✦Operational control and decision authority
✦Responsible official and signatory authority
◆The actor's role changes across the workflow
◆Responsibility is delegated without preserved authority
◆The submitted role does not match the operational role
05
GUIDED DETERMINATION STAGE
Resolve the controlling version
Which edition, amendment, effective date, adopted code, permit condition, contract term, or regulatory text controls?
The latest publication is not always the legally controlling publication. Adopted, incorporated, permitted, or contracted versions may differ.
✦Official source and publication date
✦Effective and compliance dates
✦Adoption or incorporation record
✦Amendment, supersession, and transition history
◆The version is unknown
◆A superseded edition is being relied upon
◆The adopted edition differs from the edition evaluated
06
GUIDED DETERMINATION STAGE
Test thresholds and exclusions
Do source size, pollutant, system class, risk category, sector, quantity, duration, affected population, or other thresholds bring the subject into scope?
Applicability often turns on defined thresholds, exclusions, exemptions, classifications, and conditional triggers rather than broad subject similarity.
✦Threshold calculations and classifications
✦Source, discharge, quantity, or risk records
✦Exemption and exclusion evidence
✦Historical and current operational data
◆Threshold data is incomplete
◆An exemption is asserted without evidence
◆Material changes may have altered classification
07
GUIDED DETERMINATION STAGE
Map required evidence
What records, measurements, methods, monitoring, testing, notices, approvals, or governance artifacts must exist?
A conclusion without the evidence required by the controlling instrument cannot become an admissible applicability determination.
✦Required monitoring and recordkeeping map
✦Approved method and instrument records
✦Chain of custody and quality assurance
✦Notices, certifications, approvals, and review records
◆Required evidence is missing or stale
◆The method is not approved for the proposition
◆Continuity or custody cannot be reconstructed
08
GUIDED DETERMINATION STAGE
Commit and revalidate
What bounded determination can be committed, and what events require the determination to be reopened?
Applicability must be preserved as a dated, attributable, reviewable finding with explicit limits and revalidation triggers.
✦Determination record and reviewer identity
✦Scope, non-scope, assumptions, and unresolved facts
✦Material-change and revalidation triggers
✦Review, challenge, correction, and supersession pathway
◆The finding overstates certainty
◆Unresolved facts are hidden
◆No revalidation trigger or review path is preserved
READINESS, PACKAGE, AND HANDOFF
The participant leaves with more than a result.
A completed route should produce a structured package that can be inspected by counsel, regulators, qualified technical reviewers, code officials, accreditation bodies, TA-14 Entity Review, or another competent authority without forcing that reviewer to reconstruct the entire question from scattered documents.
Identity, jurisdiction, role, version, or threshold facts remain too incomplete to begin a defensible determination.
The subject and instrument are bounded, but required evidence, authority, or exclusions remain incomplete.
The package is organized, limitations are declared, and unresolved questions are visible to a competent reviewer.
A bounded finding has been committed with reviewer identity, evidence, scope, limitations, and revalidation triggers.
APPLICABILITY FAILURE MODES
The institution must preserve how a conclusion can fail.
Most dangerous applicability errors are not caused by an absent instrument. They occur when the wrong version, authority, role, jurisdiction, threshold, or evidence is silently substituted for the controlling one.
Keyword applicability
A system declares an instrument applicable because a matching word appears in the profile.
TA-14 RESPONSE
Require subject, role, jurisdiction, version, threshold, and evidence resolution before any determination.
Latest-edition substitution
The newest standard or code is treated as controlling even though another edition was adopted or incorporated.
TA-14 RESPONSE
Preserve the adopted edition, effective date, local modification, and supersession path.
Authority collapse
Guidance, voluntary standards, contracts, regulations, and statutes are treated as if they carry identical force.
TA-14 RESPONSE
Classify the instrument and preserve the actual authority pathway that makes it applicable.
Role mismatch
A duty assigned to one actor is incorrectly imposed on or removed from another actor.
TA-14 RESPONSE
Bind each obligation to the actual provider, deployer, owner, operator, discharger, generator, or other accountable role.
Unsupported exemption
An exclusion or exemption is asserted without preserving the facts and evidence necessary to support it.
TA-14 RESPONSE
Treat the route as HOLD until the exemption conditions are proved and versioned.
Jurisdiction drift
A system, facility, product, or affected population moves into a new jurisdiction while the old determination remains active.
TA-14 RESPONSE
Trigger mandatory revalidation after location, market, permit, authority, or affected-person change.
Evidence substitution
General organizational evidence is used in place of the source-specific, system-specific, or activity-specific evidence required.
TA-14 RESPONSE
Reject substituted evidence unless the controlling instrument expressly permits it for the bounded proposition.
Applicability treated as permission
A finding that an instrument applies is mistaken for authorization to execute the underlying action.
TA-14 RESPONSE
Separate applicability from approval, permit, certification, admissibility, commitment, execution, and outcome verification.
TA-14ACADEMYAPPLICABILITY DETERMINATION
THE ACADEMY INSIDE APPLICABILITY
Understand why an instrument applies before relying on the result.
The Academy teaches the difference between law, regulation, standard, code, framework, guidance, contract, and institutional architecture. It also teaches how jurisdiction, adoption, version, role, thresholds, exemptions, evidence, and material change affect the determination.
Instrument classification
Distinguish statutes, regulations, standards, codes, guidance, frameworks, contracts, and proposals.
Authority resolution
Identify who issued, adopted, enforces, interprets, certifies, or relies upon the instrument.
Jurisdiction mapping
Resolve federal, state, tribal, territorial, local, international, sectoral, and contractual scope.
Version control
Preserve the edition, amendment, effective date, transition rule, and adopted local modification.
Threshold analysis
Test classifications, quantities, source categories, risk levels, affected populations, and exemptions.
Evidence sufficiency
Map the required records, methods, monitoring, quality assurance, notices, and reviewer evidence.
Determination writing
Create a bounded finding with scope, non-scope, assumptions, confidence, and unresolved questions.
Revalidation
Recognize material changes that require the prior applicability finding to be reopened.
ABBoundary
INSTITUTIONAL APPLICABILITY BOUNDARY
A preliminary result is not legal advice, regulatory approval, certification, or permission to execute.
The workspace helps assemble the questions, authorities, evidence, versions, and boundaries required for competent review. Final applicability may require regulators, counsel, qualified technical professionals, adopted codes, permit authorities, accredited bodies, or other competent decision-makers.