Which authority, document and evidence type answers the question? Learn to replace an expansive compliance claim with a precise statement, a traceable source and a useful next action.
10 connected sections12 claims to audit75–100 min · estimatedOfficial sources checked 2026-09-09
01 / 10
One sales claim hides several systems
“FCC/CE/Bluetooth certified worldwide.” What, exactly, could an engineer sign beneath that sentence?
The condition-monitoring node has reached a sales review. A slide combines a laboratory report, a module identifier and an industry record into one confident line. Each document may be useful. The error happens at the join: the sentence assigns all three the same issuer, scope and effect, then expands them to every market.
Think about itWhich words in that sales claim concern a declaration, a marking, government authorization or an industry program?
Answer
FCC points toward a US government equipment route. CE is a conformity marking associated with applicable EU obligations, including a manufacturer’s declaration under RED. Bluetooth points to a separate specification and qualification ecosystem. None of those words identifies the node, antenna, territory, date or issuer of the actual record. The word “worldwide” has no supporting trace.
Annotate the sentence before correcting itScroll sideways if the table extends beyond its frame.
Missing item
Why the omission changes the question
Product identity
Node or gateway? Module or complete host? Which HW/FW and antenna?
Territory and activity
Placing/marketing, import, operation and qualification are distinct.
Issuer and document role
A report, declaration, government record and industry record cannot substitute for each other.
Date and scope
Read the document for this activity and configuration, then check its source status.
All product records in this lesson are an illustrative engineering case. The inherited generic 2.450 GHz QPSK waveform is not automatically Bluetooth, Wi-Fi or a legally permitted radio mode. C07/C08 explicitly discuss a proposed Bluetooth variant with its exact specification still unknown. Actual-source cards below are a separate dataset. [FCC-AUTH][RED][BT-QUAL]
Engineering decision → record update
Open p09-compliance-register-v1, snapshot p09-m01-authority-register-v1. Retain the sales sentence as material to audit. Add separate source-role questions rather than a “certified worldwide” field.
02 / 10
Allocation is not permission for a product
If the frequency fits the table, why is the product question still unanswered?
An allocation organizes spectrum use by services and conditions. An assignment, in the ITU vocabulary, concerns an administration’s authorization for a station to use a frequency or channel. That difference changes the scale of the question: a service-level table entry cannot identify this node’s configuration or its permitted activity. The ITU release page identifies the 2024 edition; the actual definitions are in Volume 1, Nos. 1.16–1.18. [ITU-RR]
Original explanatory diagram. Arrows mean “informs the next question,” never automatic permission. Text equivalent: allocation concerns a service context; national use rules and configured-product obligations need separate records; qualification answers an industry question. Sources: [ITU-RR], [FCC-USE], [BT-QUAL].
The diagram is a source route, not a universal administrative sequence. A national framework may provide a licence exemption with conditions, or require a specific authorization. Determine that from the relevant national rules. Do not invent a requirement for an individual licence merely because allocation is insufficient. In the US example, §15.5 attaches interference conditions to operation and says prior certification does not establish a continued right to a frequency. [FCC-USE]
Common misconceptionInternational allocation authorizes national operation.
C01 supplies an allocation and requests permission for a node. The primary issue is the evidence role. Even a correctly read, recently reviewed allocation leaves the configured-product and national-use questions open.
Engineering decision → record update
P09-M01-C01-v1: route national use conditions to the national spectrum authority. Keep product market requirements as a separate question; do not infer permission from 2.450 GHz.
03 / 10
Identify the document before reading the requirement
What makes a sentence a requirement for this product?
Identify the issuer and the document’s legal role before interpreting its verbs. A legislature’s act, a binding regulator rule, a delegated or implementing measure, and an explanatory guide do different jobs. A regulator can publish all of them on the same domain. “Shall” in a vendor guide still needs a trace to the applicable requirement; a logo and a forceful verb cannot establish applicability.
Document role precedes requirement interpretationScroll sideways if the table extends beyond its frame.
Role
What to record before using it
Legislative act / regulator rule
Authority, scope, activity, operative text and relevant amendments.
Delegated / implementing measure
Its enabling act, subject, product categories and application provisions.
Consolidated reading text
Version date and included amendments; distinguish the reading aid from the authentic acts.
Official guidance
The rule it explains, author, date and limitations; do not relabel it as legislation.
Think about itA guidance page was updated yesterday; the relevant law is older. Which one sets the legal requirement?
Answer
Recency does not promote guidance into law. Read the applicable legal text and amendments, then use the guide to navigate the explanation. A newer source with the wrong role cannot replace an older source with the right role. Record both and their distinct purposes.
Actual source trace 1 · law and explanation
The RED original-act page identifies Directive 2014/53/EU and links to the consolidation dated 2026-05-30. Article 16 links presumption of conformity to the requirements covered by cited harmonised standards. The Commission’s harmonised-standards page explains voluntary use. The first supplies legislative wording; the second is an explanation. Neither says that downloading the newest PDF automatically establishes conformity of the node. [RED][EU-HS]
Engineering decision → record update
P09-M01-C02-v1 and C03-v1: add an authority/role field and keep citation, covered requirements, activity and date open. This researched trace has no synthetic support attestation or “claim complete” status.
04 / 10
Standards and test organizations have different jobs
A lab is excellent at testing. Does that give it authority to approve every market?
A technical specification describes requirements or characteristics. A test method describes how evidence is obtained. A legal citation can give a standard a defined role in demonstrating covered requirements. These are three relationships to investigate, even when a single document contains both requirements and methods.
Now separate organizations from documents. Laboratory competence concerns the work the laboratory can perform. Accreditation records define an assessed scope. A regulator’s recognition is another fact. A conformity-assessment or certification body performs the decisions allowed by its particular appointment or recognition. One company may host several services; its laboratory report and certification decision still need distinct record identities.
Competence, recognition and decision authorityScroll sideways if the table extends beyond its frame.
Evidence
Supported inference / remaining question
ISO/IEC 17025 public scope
Concerns laboratory competence, impartiality and consistent operation. It is not an actual lab’s accreditation certificate.
Actual accreditation scope
Inspect covered methods, locations and conditions; accreditation alone is not every regulator’s recognition.
ISED recognition
RSS-Gen separately addresses certification bodies (§3.7) and testing laboratories (§3.8.1), including their recognized scopes.
Scoped body decision
Identify the product, jurisdiction and permitted decision; do not extend it by the lab’s reputation.
ISO’s public scope explanation was read; the full protected normative text was not. ISED’s actual requirements distinguish body and lab recognition. C04’s synthetic accreditation record can support a competence question but cannot supply an all-market product decision. [ISO-LAB][ISED-GEN]
Go deeperNormative references and source precedence
A normative reference can bring another document’s requirements into the referring document’s scope; the reference still needs a version and applicability analysis. Informative material explains. Neither label alone says whether the document is legally mandatory. For the US source trace, §2.910’s incorporation wording specifies an edition mechanism; it is not a “newest PDF wins” rule. If sources appear inconsistent, record the conflict and ask the competent reviewer to resolve authority, timing and scope. Do not let an interface sort order decide precedence. [FCC-AUTH]
Engineering decision → record update
P09-M01-C04-v1: request the laboratory scope and relevant recognition record, then ask which body or responsible actor owns the market decision.
05 / 10
Name the exact kind of decision or record
What kind of record is hidden behind the word “certified”?
Use the exact name of the decision or record in its jurisdiction. “Certified” on its own does not identify the decision maker, criteria or covered equipment. Certification, declaration and marking can participate in a route without being synonyms. A test result is evidence within a defined question; the route determines what else is required.
Vocabulary with explicit jurisdiction and document roleScroll sideways if the table extends beyond its frame.
Term / context
Meaning to investigate
What it does not establish alone
Certification · US Part 2
A scoped equipment-authorization decision; inspect §2.907 and the actual record.
Canadian permission or unspecified product variants.
Supplier’s declaration · US
The responsible party’s procedure under §2.906.
The same document or actor as an EU declaration.
EU declaration / CE marking
Manufacturer declaration and associated conformity marking under RED.
A laboratory-issued worldwide certificate.
Listing · Canada
Identify the relevant REL entry and its regulatory context.
A licence to operate or industry qualification.
Registration
Ask what is registered, with whom, under which scheme and for what effect.
Universal technical approval simply because an identifier exists.
Authorization / approval / homologation
Read the term in the particular legal or program system; identify issuer and conditions.
One universal route shared by all jurisdictions.
RED Article 10(3) connects the manufacturer’s conformity assessment, declaration and marking; Article 18(4) assigns responsibility through the declaration. The US provisions use their own certification and responsible-party vocabulary. Canada’s listing and certification provisions require their own source trace. Preserve those terms rather than renaming every record “certificate.” [RED][FCC-AUTH][ISED-GEN]
Common misconceptionCE is a laboratory-issued world certificate.
C05’s report may answer a test question. Its existence does not identify the manufacturer’s declaration, applicable route, or every product configuration. The repair names the report’s limited contribution before assigning the missing route review.
Engineering decision → record update
P09-M01-C05-v1 and C06-v1: record the exact document type, issuer and territory. A US identifier stays in its US scope while the Canadian question receives its own source route.
06 / 10
Industry qualification is a separate evidence lane
If the product interoperates and carries an industry record, which question remains?
A technology specification defines behavior. Interoperability evidence tests behavior between implementations under stated conditions. Qualification addresses an industry program, which can also involve licence and branding obligations. These questions matter to the proposed Bluetooth node variant, but they do not identify its national operating conditions or government market route.
Actual source trace 2 · alliance and government
Bluetooth SIG’s qualification page describes a program tied to Bluetooth specifications and licence agreements, including trademark licensing. Its specification catalogue lists document versions and statuses. Separately, FCC Part 2 describes equipment-authorization procedures. Reading these sources supports a separation of questions; it is not evidence that the fictional variant satisfies either program. [BT-QUAL][BT-SPECS][FCC-AUTH]
C07 and C08 cross the lanes in opposite directionsScroll sideways if the table extends beyond its frame.
Supplied evidence
Question it leaves unanswered
C07 · synthetic Canadian certificate
Does the named Bluetooth product satisfy the current alliance qualification and branding requirements?
C08 · synthetic industry record
Which official product and operating requirements apply in the selected government jurisdiction?
The practical consequence is a missing workstream: the team could finish its RF tests while lacking a program record, or finish qualification while lacking the government evidence. Keep each owner and each unresolved fact visible. Do not attach Bluetooth labels to the generic QPSK teaching waveform to make the narrative convenient.
Engineering decision → record update
P09-M01-C07-v1 belongs to an alliance reviewer question. C08-v1 opens a government question. Neither closes the other lane.
07 / 10
Responsibility follows the market role
Who has to act when the evidence is incomplete?
Responsibility follows the legal market role, not the organization chart or whoever booked the laboratory. An engineering team may prepare evidence while a different entity carries the legal duty. Before assigning a task, record which jurisdiction supplies the role definition and which entity occupies it.
Actor-to-task source map · examples, not appointments for the fictional nodeScroll sideways if the table extends beyond its frame.
Actor / context
Source-backed task orientation
Question to assign
Manufacturer · EU RED Art.10
Owns conformity assessment, documentation and declaration/marking duties.
Which entity places this design under its name?
Importer · EU RED Art.12
Checks the required conformity work and accompanying information before placement.
Who brings the product from a third country into this market?
Distributor · EU RED Art.13
Exercises due care and verifies specified markings/documents.
Which checks apply to this supply activity?
Authorized representative · EU RED Art.11
Performs tasks in a written mandate; specified manufacturer duties are excluded.
What exactly does the mandate cover?
Responsible party / grantee · US §2.909
Responsibility depends on the authorization procedure and modification context.
Who holds the grant or fulfills the responsible-party role?
Responsible supplier · other jurisdictions
A role name requiring its own national definition; no universal mapping supplied here.
Which actual law defines that role in the target market?
Laboratory / recognized body
Test competence and decision authority are independently scoped.
Which method and decision are within the recognized scope?
The table uses RED’s actor provisions, the US responsible-party rule and ISED’s recognition provisions as bounded examples. It does not name a real manufacturer, importer, grantee or reviewer for the node. The router’s actors are fictional assignments to review a question. A complete exercise owner field is not a legal appointment. [RED][FCC-AUTH][ISED-GEN]
Engineering decision → record update
Every C01–C12 row gets a next owner and explicit responsibility. Leave the actual jurisdiction-responsible legal entity unresolved until the supply chain and product route are known.
08 / 10
A claim belongs to a configuration and activity
What did the report test: a module, a host, or the product you plan to ship?
A module record can be strong evidence for its stated module and still leave host integration unanswered. Firmware settings, antenna/cable, enclosure, concurrent transmitters, supply/accessories and user installation can change the question. Record these facts without pretending every difference necessarily requires the same test or procedure. Module 09.2 owns the detailed configuration coverage analysis.
Illustrative manifest boundary · inherited identities remain intactScroll sideways if the table extends beyond its frame.
Known context
Still unresolved for market review
teaching-node-v1 · generic 2.450 GHz QPSK
Final standardized mode, product SKU and region configuration.
M08-01-RAW-A → M08-01-DERIVED-A
Those bench records do not cover every shipped host or antenna.
Node / gateway product story
Final HW/FW, antenna, cable, enclosure, supply, concurrent modes and installation.
07.1 C-MARKET
A market question is inherited; no official applicability decision is inherited.
Also split the activity. “Sell and operate in GB and NI” contains at least four territory/activity questions. A national-use question must not disappear because a product-marketing question was easier to route. C11’s paired-territory statement produces visible children with the same parent. Its unsupported indefinite transfer remains an issue in each child until repaired.
Atomic child records · no winning territory or default US laneScroll sideways if the table extends beyond its frame.
Child / parent
Territory / activity
Remaining action
SALES-GB-NI-1 / SALES-GB-NI
GB / placing/marketing
Read this territory’s source; do not transfer a marking conclusion.
SALES-GB-NI-2 / SALES-GB-NI
NI / placing/marketing
Read this territory’s source; do not transfer a marking conclusion.
Think about itAn in-scope pre-compliance result supports a design decision. Does that close market access?
Answer
No. Evidence scope and maturity are independent. A pre-scan can be useful within its actual method and configuration while lacking the role of a formal route record. C10 stays challenge when its report is called market authorization. Keep the useful observation and replace the unsupported conclusion.
Engineering decision → record update
P09-M01-C09-v1 preserves unknown host/antenna coverage; C10-v1 preserves the pre-scan’s design value. Hand off the manifest gaps to 09.2 without generating fake approvals.
09 / 10
Read dates and source status independently
Which date changed: the law, the document, the activity or your last review?
Publication identifies when text appeared. Entry into force and application may differ. A transition may permit particular editions for particular activities. Source access says when someone retrieved the source; a review date says when its relevance was assessed. An editorial due date schedules a recheck. These are separate fields because collapsing them into “expiry” can misstate both current and historical evidence.
RSS-Gen Issue 6, dated 2026-07-30, describes a one-year transition from publication during which applications and compliance with Issue 5 or Issue 6 are accepted. That is an example of why an older edition can remain relevant during a stated transition; the node’s eligibility and all applicable RSS requirements still need review. The lesson does not replace that wording with its synthetic quarterly deadline. [ISED-GEN]
Date and status examples · keep legal events and editorial review separateScroll sideways if the table extends beyond its frame.
Record
What the date can establish
Actual RED consolidation · 2026-05-30
Identifies the reading version reached from the original; not the access date.
Actual GB/NI guides · updated 2025-12-16
Identifies the displayed guidance update, not a timeless legal route.
Actual sources accessed · 2026-09-09
A research attestation separate from the synthetic fixture freeze.
Review current through Dec 7; overdue on Dec 8. No legal expiry implied.
Superseded but scoped historical card
Retain when explicitly relevant to the historical activity; otherwise inspect relevance.
The GB and NI guides were read separately. They describe different marking contexts; a UKCA summary does not establish NI placement. A page can be up to date and still have only a guidance role. A newly dated vendor summary remains a vendor summary. C12 must preserve both its authority problem and unknown dates. [UK-GB][UK-NI]
Common misconceptionThe most recent summary must determine the current route.
Add a date to C12 and the authority mismatch survives. Conversely, an overdue editorial review asks for a recheck; it does not itself prove a factual error or revoke a grant.
Engineering decision → record update
P09-M01-C11-v1 and C12-v1: record publication, entry into force, application/transition, access, review, review due and evaluation separately. Reopen on a changed source, territory, activity or product.
10 / 10
Repair the claim and assign the next question
Can you leave the review with a better sentence and an accountable next step?
The router accepts curated metadata, not natural-language legal interpretation. Read its supplied source card, compare the requested and supported inference, then decide whether to challenge the assertion or inspect a gap. The two incomplete questions, C03 and C09, are deliberately not treated as false assertions simply because decisive facts are missing.
Select C08 and predict whether qualification is enough. Read both evidence lanes.
Reframe the government question; identify the source category and reviewer. Notice that “routed” makes no product decision.
Select C09 and expose the unknown host scope. Compare the incomplete summary with a scoped host-review question.
Select C12, then load “add dates only.” Explain why the authority issue remains.
Write a scoped next question in the custom copy, apply it, then reset. Reset restores every defining fact and date.
Class 1 · Authority & Evidence Router
Challenge the inference. Route the next question.
Each card is fictional and marked Illustrative. Default: 10 challenge / 2 inspect / 0 routed. All twelve claims stay in the evidence universe.
This exercise supports engineering source and evidence review. It does not decide legal applicability or authorize a product. A qualified specialist must resolve the named route, host and market questions.
The ITU allocation authorizes this node nationally.
Scoped replacement · suggested wording
The allocation describes a service-level frequency context. National use conditions and this node’s product route remain open. Ask the national spectrum authority which operating rules and product facts need review.
This comparison changes no evidence. Use “Reframe as review question” to change the requested conclusion.
Government lane
Product requirements, authorized configurations and operating conditions. Selected question in this lane. Legal validity: not evaluated.
Industry lane
Technical interoperability, qualification and branding. No closure inferred from a government record. Generic QPSK is not a Bluetooth implementation.
Current claim / source / role traceScroll sideways if the table extends beyond its frame.
Source identity
Role and supported inference
Read / support / scope
SYN-E-C01
international allocation A service allocation under specified conditions; no node authorization.
full text; SYN-L-C01: supports CH / operation / configuration known
Separate evidence dimensionsScroll sideways if the table extends beyond its frame.
Dimension
Current state
Scope match
matched
Evidence maturity
reference
Source review
SYN-E-C01: review current through 2026-12-07
Legal validity
Not evaluated
Known facts
Illustrative condition-monitoring node/gateway; teaching-node-v1. Generic 2.450 GHz QPSK teaching mode; no standardized radio claimed.
Missing facts
No routing metadata gap; final product applicability and configuration facts still require specialist review.
Next source category: national operating rule
CH / operation: The allocation describes a service-level frequency context. National use conditions and this node’s product route remain open. Ask the national spectrum authority which operating rules and product facts need review.
Owner: national spectrum authority. Recheck before the named activity, on document/product/territory change, or after 2026-12-07.
P09-M01-C01-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The allocation describes a service-level frequency context. National use conditions and this node’s product route remain open. Ask the national spectrum authority which operating rules and product facts need review.
Territory / activity / intended date
CH; operation; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: national spectrum authority
Authority / document role / language
SYN-E-C01: Fictional exercise publisher — no actual authority attestation; international allocation; SYN-DOC-C01 / exercise-v1; Synthetic card C01, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
national spectrum authority: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C01: reference; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: reference
Scope match: matched
Routing: challenge
Source review: SYN-E-C01: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The allocation describes a service-level frequency context. National use conditions and this node’s product route remain open. Ask the national spectrum authority which operating rules and product facts need review.
Owner: national spectrum authority
Dates — synthetic attestations only
SYN-E-C01
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
All 12 current claims · 10 challenge / 2 inspect / 0 routedScroll sideways if the table extends beyond its frame.
Claim / template
Source IDs / roles
Baseline → current
C01 unsupported-assertion
SYN-E-C01: international allocation
challenge → challenge
C02 unsupported-assertion
SYN-E-C02: technical standard
challenge → challenge
C03 incomplete-question
SYN-E-C03: technical standard
inspect → inspect
C04 unsupported-assertion
SYN-E-C04: accreditation/recognition record
challenge → challenge
C05 unsupported-assertion
SYN-E-C05: laboratory report
challenge → challenge
C06 unsupported-assertion
SYN-E-C06: scoped product authorization record
challenge → challenge
C07 unsupported-assertion
SYN-E-C07: scoped product authorization record
challenge → challenge
C08 unsupported-assertion
SYN-E-C08: industry qualification record
challenge → challenge
C09 incomplete-question
SYN-E-C09: scoped product authorization record
inspect → inspect
C10 unsupported-assertion
SYN-E-C10: laboratory report
challenge → challenge
C11 unsupported-assertion
SYN-E-C11: vendor statement
challenge → challenge
C12 unsupported-assertion
SYN-E-C12: vendor statement
challenge → challenge
The exact routing contract
Evaluate identity/schema, atomic scope, evidence role, reading/support, source review/status, then next source and owner. An invalid input has no current evaluated result. A challenge takes precedence over inspect but retains missing facts. Routed means the next question and owner are coherent. Applicability, evidence maturity, scope match, source review and legal validity stay separate.
Stable reason order: invalid-identity → scope-conflict → wrong-authority → wrong-territory → unsupported-inference → missing-fact → unread-source → review-overdue → next-action; then claim ID, source ID and detail. Dates use Gregorian ISO date-only values and UTC, never the browser clock. Impossible dates and future access/review attestations are invalid; a future announced application date is allowed. Maximum: 12 claims, 24 source cards and 36 support edges. Rule outcomes use exact identity/status/reason comparisons; no floating-point tolerance applies.
Twelve canonical original / corrected pairs · all IllustrativeScroll sideways if the table extends beyond its frame.
ID / default status
Original audit material
Scoped replacement
C01 · challenge
The ITU allocation authorizes this node nationally.
The allocation describes a service-level frequency context. National use conditions and this node’s product route remain open. Ask the national spectrum authority which operating rules and product facts need review.
C02 · challenge
This voluntary standard is the law everywhere.
The standard supplies technical requirements within its own scope. Its legal use in any market depends on the relevant law and incorporation or citation. Ask the product-regulatory specialist to establish that relationship for each territory.
C03 · inspect
The newest standards PDF is supplied; its citation and route coverage are unspecified.
The PDF identifies a technical revision. Citation, covered requirements and the activity date remain unknown. Ask the product-regulatory specialist which official citation and route apply to the intended product.
C04 · challenge
An accredited lab approved every market.
The accreditation record concerns a laboratory’s defined competence. Market-specific recognition and decision authority remain separate. Ask the competent laboratory for its scope and the product-regulatory specialist for each market route.
C05 · challenge
CE is a laboratory-issued world certificate.
The laboratory report records a test of its stated specimen. It is not a worldwide CE certificate. Ask the EU manufacturer’s responsible reviewer for the applicable conformity procedure, declaration and marking basis.
C06 · challenge
An FCC ID authorizes the same configuration in Canada.
The supplied US authorization record concerns its stated US scope. Canadian requirements and records remain open. Ask the Canadian product-regulatory specialist for the ISED sources and configuration review.
C07 · challenge
A Canadian radio certificate grants Bluetooth qualification.
The Canadian certificate concerns its Canadian regulatory scope. It leaves Bluetooth qualification and branding unresolved. Ask the alliance program owner for the current qualification requirements for the named Bluetooth variant.
C08 · challenge
Bluetooth qualification closes government market access.
The industry record concerns qualification of its stated Bluetooth product. Government market access remains open. Ask the product-regulatory specialist for the target territory’s official product and operating-rule sources.
C09 · inspect
The module has a scope record; coverage of this host and antenna is unspecified.
The module record identifies a module scope; host and antenna coverage remain unknown. Which host conditions require review? Ask the recognized body to inspect the grant, integration instructions and proposed host configuration.
C10 · challenge
The pre-scan report is market authorization.
The pre-scan informs design for its stated setup. It cannot establish market authorization. Ask the product-regulatory specialist which formal route, configuration coverage and evidence remain necessary.
C11 · challenge
UKCA proves the same route for GB and NI indefinitely.
The vendor summary describes a marking claim. It does not establish one perpetual GB/NI route. Ask the product-regulatory specialist to open separate dated GB and NI records using current official sources.
C12 · challenge
This undated vendor summary determines the current route.
The vendor summary supplies a lead, not authority to determine the route. Its provenance and dates remain unknown. Ask the product-regulatory specialist to locate, read and date the actual official source.
Changed-input counterexamples · static and no-script evidenceScroll sideways if the table extends beyond its frame.
Changed input
Exact focal outcome
Why
C12 · add dates only
C12: challenge
Known dates remove unknown-date. The vendor role still cannot establish a government route.
C09 · ask the host question
C09: routed
The requested conclusion is a scoped next question with an owner. Unknown host facts remain named; no host approval follows.
C03 · newer, still uncited
C03: inspect
A new revision does not supply the missing citation, activity date or route coverage.
C03 · assert automatic conformity
C03: challenge
An explicit unsupported conclusion takes precedence over the existing unknown facts.
C09 · assert blanket host coverage
C09: challenge
The missing host evidence remains visible alongside unsupported-inference.
C01 · a general definition
C01: routed
A definition question can identify the appropriate source without an antenna manifest or product territory.
C09 repaired · on review due date
C09: routed
Review is current through 2026-12-07 under the exercise’s inclusive UTC date rule.
C09 repaired · following day
C09: inspect
On 2026-12-08 the snapshot needs rechecking. No grant or historical report is revoked.
C09 repaired · historical source
C09: routed
A superseded source remains available for an explicitly reviewed activity within its historical scope.
Closed source-role map · possible review use, never automatic sufficiencyScroll sideways if the table extends beyond its frame.
Role
Next question this kind of source can help answer
international allocation
What service and frequency context is defined?
national operating rule
Which national use conditions apply?
product-market law/rule
Which product/activity obligations need review?
official guidance
Which rule is being explained?
technical standard
What technical characteristics or requirements are specified?
method
How should the relevant evidence be obtained?
accreditation/recognition record
Which competence or recognition scope is recorded?
scoped product authorization record
What product, configuration and jurisdiction does the decision cover?
declaration
Who declares what under which legal framework?
laboratory report
What was tested under which conditions?
industry qualification record
Which industry product/program scope is covered?
vendor statement
What lead needs verification from an actual authoritative source?
Synthesis · one-page authority map · Illustrative
Question → source → owner → open facts
Start with one product, territory, activity and date. Preserve the supplied document and write only the inference it supports.
Review assignmentsScroll sideways if the table extends beyond its frame.
Applicable product law and scoped route records / product-regulatory specialist and jurisdiction-responsible actor
Competence · C04
Accreditation and recognition scope / competent laboratory
Industry qualification · C07
Program sources / alliance program owner
Host conditions · C09
Scoped grant and integration instructions / recognized body
Open product facts: final SKU/HW/FW/region, host/antenna/cable, radio mode/concurrency, enclosure, supply/accessories, user/installation/environment. Open decisions: legal applicability, actual responsible entity, exact method and route.
Two actual traces: RED Article 16 → Commission explanation; Bluetooth program → separate FCC route. Sources accessed 2026-09-09. Synthetic evaluation: 2026-09-08; review due 2026-12-07. Deliver P09-M01-C01-v1 through C12-v1 with the corrected statements and complete rows below.
Complete authority-register snapshot
p09-compliance-register-v1 / p09-m01-authority-register-v1. Every disclosure contains the full row, including the same explicit manifest, technical-value boundary and separate dates. Applicability remains unknown in all twelve rows. An eventual “not applicable” needs its own reviewed rationale; blank evidence is never an exemption.
Register index · canonical snapshot, independent of interactive editsScroll sideways if the table extends beyond its frame.
P09-M01-C01-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The allocation describes a service-level frequency context. National use conditions and this node’s product route remain open. Ask the national spectrum authority which operating rules and product facts need review.
Territory / activity / intended date
CH; operation; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: national spectrum authority
Authority / document role / language
SYN-E-C01: Fictional exercise publisher — no actual authority attestation; international allocation; SYN-DOC-C01 / exercise-v1; Synthetic card C01, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
national spectrum authority: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C01: reference; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: reference
Scope match: matched
Routing: challenge
Source review: SYN-E-C01: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The allocation describes a service-level frequency context. National use conditions and this node’s product route remain open. Ask the national spectrum authority which operating rules and product facts need review.
Owner: national spectrum authority
Dates — synthetic attestations only
SYN-E-C01
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C02-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The standard supplies technical requirements within its own scope. Its legal use in any market depends on the relevant law and incorporation or citation. Ask the product-regulatory specialist to establish that relationship for each territory.
Territory / activity / intended date
unknown; placing/marketing; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: product-regulatory specialist
Authority / document role / language
SYN-E-C02: Fictional exercise publisher — no actual authority attestation; technical standard; SYN-DOC-C02 / exercise-v1; Synthetic card C02, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
product-regulatory specialist: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C02: reference; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: reference
Scope match: unknown
Routing: challenge
Source review: SYN-E-C02: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The standard supplies technical requirements within its own scope. Its legal use in any market depends on the relevant law and incorporation or citation. Ask the product-regulatory specialist to establish that relationship for each territory.
Owner: product-regulatory specialist
Dates — synthetic attestations only
SYN-E-C02
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C03-v1; parent: none — original row; 09.1; Illustrative
incomplete-question; The PDF identifies a technical revision. Citation, covered requirements and the activity date remain unknown. Ask the product-regulatory specialist which official citation and route apply to the intended product.
Territory / activity / intended date
EU/EEA; placing/marketing; unknown
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: product-regulatory specialist
Authority / document role / language
SYN-E-C03: Fictional exercise publisher — no actual authority attestation; technical standard; SYN-DOC-C03 / exercise-v1; Synthetic card C03, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
product-regulatory specialist: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C03: reference; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: reference
Scope match: matched
Routing: inspect
Source review: SYN-E-C03: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
route-coverage; Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The PDF identifies a technical revision. Citation, covered requirements and the activity date remain unknown. Ask the product-regulatory specialist which official citation and route apply to the intended product.
Owner: product-regulatory specialist
Dates — synthetic attestations only
SYN-E-C03
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C04-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The accreditation record concerns a laboratory’s defined competence. Market-specific recognition and decision authority remain separate. Ask the competent laboratory for its scope and the product-regulatory specialist for each market route.
Territory / activity / intended date
unknown; placing/marketing; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: competent laboratory
Authority / document role / language
SYN-E-C04: Fictional exercise publisher — no actual authority attestation; accreditation/recognition record; SYN-DOC-C04 / exercise-v1; Synthetic card C04, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
competent laboratory: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C04: reference; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: reference
Scope match: unknown
Routing: challenge
Source review: SYN-E-C04: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The accreditation record concerns a laboratory’s defined competence. Market-specific recognition and decision authority remain separate. Ask the competent laboratory for its scope and the product-regulatory specialist for each market route.
Owner: competent laboratory
Dates — synthetic attestations only
SYN-E-C04
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C05-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The laboratory report records a test of its stated specimen. It is not a worldwide CE certificate. Ask the EU manufacturer’s responsible reviewer for the applicable conformity procedure, declaration and marking basis.
Territory / activity / intended date
EU/EEA; placing/marketing; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: jurisdiction-responsible actor
Authority / document role / language
SYN-E-C05: Fictional exercise publisher — no actual authority attestation; laboratory report; SYN-DOC-C05 / exercise-v1; Synthetic card C05, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
jurisdiction-responsible actor: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C05: formal; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: formal
Scope match: matched
Routing: challenge
Source review: SYN-E-C05: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The laboratory report records a test of its stated specimen. It is not a worldwide CE certificate. Ask the EU manufacturer’s responsible reviewer for the applicable conformity procedure, declaration and marking basis.
Owner: jurisdiction-responsible actor
Dates — synthetic attestations only
SYN-E-C05
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C06-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The supplied US authorization record concerns its stated US scope. Canadian requirements and records remain open. Ask the Canadian product-regulatory specialist for the ISED sources and configuration review.
Territory / activity / intended date
CA; placing/marketing; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: product-regulatory specialist
Authority / document role / language
SYN-E-C06: Fictional exercise publisher — no actual authority attestation; scoped product authorization record; SYN-DOC-C06 / exercise-v1; Synthetic card C06, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
product-regulatory specialist: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C06: formal; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: formal
Scope match: mismatch
Routing: challenge
Source review: SYN-E-C06: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The supplied US authorization record concerns its stated US scope. Canadian requirements and records remain open. Ask the Canadian product-regulatory specialist for the ISED sources and configuration review.
Owner: product-regulatory specialist
Dates — synthetic attestations only
SYN-E-C06
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C07-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The Canadian certificate concerns its Canadian regulatory scope. It leaves Bluetooth qualification and branding unresolved. Ask the alliance program owner for the current qualification requirements for the named Bluetooth variant.
Territory / activity / intended date
CA; qualification; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Industry qualification (separate lane)
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: alliance program owner
Authority / document role / language
SYN-E-C07: Fictional exercise publisher — no actual authority attestation; scoped product authorization record; SYN-DOC-C07 / exercise-v1; Synthetic card C07, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
alliance program owner: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C07: formal; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: formal
Scope match: matched
Routing: challenge
Source review: SYN-E-C07: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The Canadian certificate concerns its Canadian regulatory scope. It leaves Bluetooth qualification and branding unresolved. Ask the alliance program owner for the current qualification requirements for the named Bluetooth variant.
Owner: alliance program owner
Dates — synthetic attestations only
SYN-E-C07
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C08-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The industry record concerns qualification of its stated Bluetooth product. Government market access remains open. Ask the product-regulatory specialist for the target territory’s official product and operating-rule sources.
Territory / activity / intended date
US; placing/marketing; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: product-regulatory specialist
Authority / document role / language
SYN-E-C08: Fictional exercise publisher — no actual authority attestation; industry qualification record; SYN-DOC-C08 / exercise-v1; Synthetic card C08, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
product-regulatory specialist: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C08: formal; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: formal
Scope match: matched
Routing: challenge
Source review: SYN-E-C08: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The industry record concerns qualification of its stated Bluetooth product. Government market access remains open. Ask the product-regulatory specialist for the target territory’s official product and operating-rule sources.
Owner: product-regulatory specialist
Dates — synthetic attestations only
SYN-E-C08
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C09-v1; parent: none — original row; 09.1; Illustrative
incomplete-question; The module record identifies a module scope; host and antenna coverage remain unknown. Which host conditions require review? Ask the recognized body to inspect the grant, integration instructions and proposed host configuration.
Territory / activity / intended date
US; placing/marketing; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: recognized certification/conformity body
Authority / document role / language
SYN-E-C09: Fictional exercise publisher — no actual authority attestation; scoped product authorization record; SYN-DOC-C09 / exercise-v1; Synthetic card C09, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
recognized certification/conformity body: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Applicability: unknown
Evidence maturity: formal
Scope match: unknown
Routing: inspect
Source review: SYN-E-C09: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The module record identifies a module scope; host and antenna coverage remain unknown. Which host conditions require review? Ask the recognized body to inspect the grant, integration instructions and proposed host configuration.
Owner: recognized certification/conformity body
Dates — synthetic attestations only
SYN-E-C09
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C10-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The pre-scan informs design for its stated setup. It cannot establish market authorization. Ask the product-regulatory specialist which formal route, configuration coverage and evidence remain necessary.
Territory / activity / intended date
EU/EEA; placing/marketing; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: product-regulatory specialist
Authority / document role / language
SYN-E-C10: Fictional exercise publisher — no actual authority attestation; laboratory report; SYN-DOC-C10 / exercise-v1; Synthetic card C10, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
product-regulatory specialist: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C10: pre-compliance; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: pre-compliance
Scope match: matched
Routing: challenge
Source review: SYN-E-C10: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The pre-scan informs design for its stated setup. It cannot establish market authorization. Ask the product-regulatory specialist which formal route, configuration coverage and evidence remain necessary.
Owner: product-regulatory specialist
Dates — synthetic attestations only
SYN-E-C10
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C11-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The vendor summary describes a marking claim. It does not establish one perpetual GB/NI route. Ask the product-regulatory specialist to open separate dated GB and NI records using current official sources.
Territory / activity / intended date
GB; placing/marketing; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: product-regulatory specialist
Authority / document role / language
SYN-E-C11: Fictional exercise publisher — no actual authority attestation; vendor statement; SYN-DOC-C11 / exercise-v1; Synthetic card C11, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
product-regulatory specialist: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C11: vendor; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Independent review dimensions
Applicability: unknown
Evidence maturity: vendor
Scope match: matched
Routing: challenge
Source review: SYN-E-C11: review current through 2026-12-07
Legal validity: not evaluated
Unresolved facts / next owner
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The vendor summary describes a marking claim. It does not establish one perpetual GB/NI route. Ask the product-regulatory specialist to open separate dated GB and NI records using current official sources.
Owner: product-regulatory specialist
Dates — synthetic attestations only
SYN-E-C11
publication: 2026-06-01
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: 2026-09-08
reviewed: 2026-09-08
reviewDue: 2026-12-07
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
P09-M01-C12-v1; parent: none — original row; 09.1; Illustrative
unsupported-assertion; The vendor summary supplies a lead, not authority to determine the route. Its provenance and dates remain unknown. Ask the product-regulatory specialist to locate, read and date the actual official source.
Territory / activity / intended date
CH; placing/marketing; 2026-09-08
Product configuration
id: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
product: Illustrative condition-monitoring node and gateway
sku: Final SKU identities unknown
hardware: Final HW unknown; inherited SYN-HW-A1 is only the 08.1 bench witness
firmware: Final FW/region unknown; SYN-FW-1.0 is only the 08.1 witness
radios: Generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35; no Bluetooth/Wi-Fi mode inferred
concurrency: Unknown; proposed gateway Wi-Fi and node radio need separate review
antennaCable: Final antenna/cable unknown
enclosure: Final enclosure/mount unknown
supplyAccessory: Battery node/gateway story; final supplies/accessories unknown
installationUserEnvironment: Condition monitoring; user, installation and environment definitions incomplete
inheritedRecords: C-MARKET (07.1); M08-01-RAW-A; M08-01-DERIVED-A
Applicability and rationale
Regulatory source/evidence routing; detailed requirement families unresolved
unknown: No product-specific legal applicability decision is supplied by this metadata exercise.
Reviewer: product-regulatory specialist
Authority / document role / language
SYN-E-C12: Fictional exercise publisher — no actual authority attestation; vendor statement; SYN-DOC-C12 / exercise-v1; Synthetic card C12, scope paragraph; current; English
Method / result / value definitions
No technical standard/method selected
No numerical conformity result or limit used in this row
Not used: documentary routing; generic carrier is scenario context, not a legal value
No measurement decision; route metadata evaluated by p09-m01-routing-rules-v1
Actor / responsibility
product-regulatory specialist: Fictional assigned reviewer: obtain the named source and resolve the question, not approve a product.
Evidence / configuration / version
SYN-E-C12: vendor; SYN-P09-M01-MANIFEST-v1; known routing scope; exercise-v1
Final host, antenna, firmware/region, concurrency, supply, installation and activity coverage; Applicable law, route, method and responsible legal actor
Next action: The vendor summary supplies a lead, not authority to determine the route. Its provenance and dates remain unknown. Ask the product-regulatory specialist to locate, read and date the actual official source.
Owner: product-regulatory specialist
Dates — synthetic attestations only
SYN-E-C12
publication: unknown / not supplied
entryIntoForce: unknown / not supplied
application: unknown / not supplied
transitionEnd: unknown / not supplied
access: unknown / not supplied
reviewed: unknown / not supplied
reviewDue: unknown / not supplied
Evaluation: 2026-09-08
Change dependencies
product/SKU; hardware/firmware/region; radio mode/concurrency; antenna/cable/enclosure; supply/accessories; market/activity/date; source revision/citation/status
Engineering decision → record update
Deliver the one-page map, twelve repaired statements, source traces and P09-M01-C01-v1–C12-v1. Continue to Product, Configuration & Market Matrix (09.2) with the unresolved manifest and market facts. This module does not complete the path.
Ungraded review
Check your understanding
Answer each question in your own words, then reveal the model answer.
01A frequency appears in an ITU allocation table. What does that establish for the node?
Model answer
It establishes a service-level allocation context under the table’s conditions. It does not establish permission for the configured node to operate. Ask the national spectrum authority about the location, activity and use conditions, and a product-regulatory specialist about the equipment route. Radio mode and configuration remain open.
02Does the newest technical standard automatically become the law?
Model answer
No. Identify the document’s role, the law or incorporation/citation mechanism, covered requirements, intended activity and date. C03 is inspect while these are missing. Explicitly claiming automatic conformity adds unsupported-inference and changes it to challenge. A current catalogue entry supplies revision identity, not proof of the legal route.
03An accredited laboratory has tested the node. What is still unknown?
Model answer
The report supports the tests and specimen conditions it actually covers. Check accredited scope, any required regulatory recognition, and the separate authority of the body making a conformity decision. Product applicability, other configurations, documentation and other markets remain unresolved; accreditation is not a world product authorization.
04Does a Bluetooth qualification record close government market access, or the reverse?
Model answer
Neither transfer follows. Qualification concerns the Bluetooth program and licence/specification obligations. A government record concerns its own jurisdiction, product and activity. Ask separate program and government questions for the explicitly named Bluetooth variant. Generic teaching QPSK has no Bluetooth status.
05What changes on 2026-12-08 when editorial review was due on 2026-12-07?
Model answer
The exercise snapshot is overdue and needs rechecking. It must not be displayed as review-current. That date is not a legal expiry and does not automatically revoke a grant or invalidate a historical report. Source supersession and any real transition rule need their own scoped review.
06The module record does not specify host or antenna coverage. What is the defensible next question?
Model answer
Ask which grant conditions, integration instructions, host/antenna facts and concurrent modes need review for the intended market activity. C09 begins as inspect. A complete review question with an assigned body and review trigger can be routed while explicitly retaining unknown host facts; “host approved” cannot be inferred.
References and further study
Actual-source access: 2026-09-09. Synthetic fixture evaluation: 2026-09-08. Sources and quoted locators were read as described below; catalogue inspection is labelled. Recheck volatile law, recognition, program and guidance claims before actual use and on revision. Specialist product applicability remains open.
ITU-RR · ITU.Radio Regulations, 2024 edition, Volume 1. 2024 edition; publisher release page also checked. Role: International treaty text. Read: Article 1, Nos. 1.16–1.18; Article 5.1. Allocation concerns services; assignment concerns an administration’s authorization to a station. No national band selection, node permission or blanket licensing conclusion. Actual provisions read; release checked at https://www.itu.int/pub/r-reg-rr
RED · European Parliament and Council / EUR-Lex.Directive 2014/53/EU, consolidated reading text. Consolidation 2026-05-30, reached from the original act. Role: Consolidated legislative reading text; amendments and original acts retain their own legal status. Read: Articles 7, 10–13, 16–20; consolidation preamble. Manufacturer responsibility, declaration, marking and cited-standard scope are distinct. No complete product applicability, national transposition or specific route determination. Original https://eur-lex.europa.eu/eli/dir/2014/53/oj/eng and current text read in a browser; original publication 2014-05-22.
EU-HS · European Commission.Harmonised standards. Live page accessed 2026-09-09; no revision number shown. Role: Official explanation. Read: Introductory explanation and “Use of harmonised standards”. Use is voluntary; publication of references and covered legal requirements must be identified. Not the RED act or a product-specific Official Journal citation. Explanatory text read; no standard selected for the node.
FCC-AUTH · FCC rules via eCFR.47 CFR Part 2, Subpart J. Displayed up to date 2026-09-04; Title 47 last amended 2026-09-03. Role: Regulator rules in the authoritative but unofficial eCFR. Read: §§2.901, 2.906–2.910; 2.948–2.950. Certification, SDoC, responsible party, incorporation and laboratory recognition answer different questions. No classification, filing, grant, method execution or Canadian permission inferred. Check later official actions before use. Text and amendment/cross-reference notices read; no delayed amendment treated as automatically operative.
FCC-USE · FCC rules via eCFR.47 CFR §15.5, General conditions of operation. Displayed up to date 2026-09-04. Role: National operating rule. Read: §15.5(a)–(c). Prior equipment certification does not create a right to continued use of a frequency; operation has interference conditions. Does not establish which Part 15 device provision applies to the fictional waveform. Actual rule read after inspecting Part 15.
ISED-GEN · ISED.RSS-Gen — General Requirements for Compliance of Radio Apparatus. Issue 6, 2026-07-30. Role: Regulator-issued technical requirements. Read: §§1, 2.2 (CB), 3.1, 3.4–3.5, 3.7–3.8.1. Category, certification, REL listing, licensing, and body/lab recognition remain separate; a stated transition exists. No radio category, band RSS, host permission or transition eligibility decided here. Actual text read; Issue 5/6 transition wording is tied to activity, not an editorial deadline.
ISED-PROGRAM · ISED.Wireless Certification. Live navigation accessed 2026-09-09. Role: Official program navigation. Read: Equipment Certification and Normative Test Standards links. An official index routes readers to the procedure and method documents. Index access does not prove reading any linked procedure. Index read; requirements sourced to RSS-Gen separately.
ISO-LAB · ISO.ISO/IEC 17025:2017. Edition 3, 2017-11; confirmed 2023. Role: Standards-body catalogue and public scope explanation. Read: Public “What is ISO/IEC 17025?” and accreditation explanation. Laboratory competence, impartiality and consistent operation differ from product certification. Full standard not accessed; no unseen normative clause asserted. A catalogue is not an actual lab’s scope record. Public scope read; catalogue-only for normative text.
BT-SPECS · Bluetooth SIG.Specifications. Accessed 2026-09-09; Core 6.3 listed Adopted. Role: Industry specification catalogue. Read: Specification/version/type/status columns. A specification listing identifies a technical document and its program status. No Core clause or product conformance inferred from the catalogue. Catalogue inspected, not full normative specification.
BT-QUAL · Bluetooth SIG.Qualify your product. Live program page accessed 2026-09-09. Role: Alliance program guidance. Read: Qualification purpose, licence agreements and product qualification instructions. Qualification addresses specification and Bluetooth licence-agreement obligations in the industry program. No government authorization, RF mode choice or actual product qualification established. Program text read; no invented qualification IDs.
UK-GB · UK Office for Product Safety and Standards.Radio Equipment Regulations 2017: Great Britain. Updated 2025-12-16; accessed 2026-09-09. Role: Official statutory guidance explaining regulations. Read: Introduction, legislative background, §9 and §11. GB has its own conformity/marking context and approved-body role. Guidance is not a product authorization or the underlying legislative instrument. Read from the government radio-equipment collection; current wording must be rechecked for the activity date.
UK-NI · UK Office for Product Safety and Standards.Radio Equipment Regulations 2017: Northern Ireland. Updated 2025-12-16; accessed 2026-09-09. Role: Official statutory guidance explaining regulations. Read: Conformity marking and glossary: UKCA, CE and UKNI. NI marking arrangements cannot be inferred from UKCA or the GB route. No perpetual route promise, actual body selection or full NI procedure supplied. NI-specific text read separately from GB.
Model authority-evidence-router/2.0; rule set p09-m01-routing-rules-v1; fixture p09-m01-claims-v1. These versions describe a curated educational router, not any law. The actual-source ledger and synthetic support records never share approval or review attestations.