Global Market-Access Strategy

01 / 10

One reused report can leave several routes open

“CE/FCC reports accepted worldwide. Can we promise the launch date?”

The condition-monitoring team already has reports and a five-market plan. A distributor now asks for Australia, Brazil, Japan and South Korea. The tempting shortcut bundles several different claims: that measurements can be used again, that their method is acceptable, that the laboratory is recognized, that the tested configuration represents the shipped product, and that the right actor can complete the receiving route. A useful report may answer the first question while the others remain open.

Carry the authority map, configuration matrix, European territory records and separate U.S./Canadian reviews forward. The source-market conformity procedures and their documents have their own scope. They do not become receiving-market conclusions because the PDF is attached to a new dossier. [EU] [US]

Evidence example · a report travels; the claim needs a new destination

A fictional N01 report names A0, one transmitter and a particular method. The expansion brief names A1 and a gateway with simultaneous radios. Keep the report immutable. Create a directed comparison from that report to one receiving requirement; annotate physical configuration and concurrency separately. A missing local signatory remains an actor question even if both RF comparisons later become supported.

Common misconceptionThe carrier is the same, so the authorization is the same.

The ITU allocation context and a national equipment or operating route answer different questions. Shared spectrum terminology does not establish allowed product conditions, methods, actors or acceptance. [ITU]

Engineering consequence → record update

Replace the worldwide claim with four dated dossier questions. Preserve the originating report, its configuration and any source-market decision as separate records; assign owners before promising a date.

02 / 10

Choose markets using explicit constraints

Market tiering is a declared project choice. Business value can tell the team which question to ask first; it cannot compensate for an unsupported mandatory condition. Use the constraint-first technology-selection method: identify hard requirements, then compare feasible options using stated preferences. Here the constraints include national operating conditions, product stability, representative samples, evidence readiness and accountable local roles.

The inherited launch baseline is EU/EEA (Germany study), Switzerland, Great Britain, United States, Canada. Northern Ireland is the explicit prior 09.3 comparison; it is not a sixth original launch market. AU, BR, JP and KR are expansion targets, not firmware-region labels already proven to work. A first-review tier means “allocate review attention”; it says nothing about regulatory difficulty or an official lead time.

Evidence example · freeze the question before freezing the image

N01 still uses the generic 2.450 GHz QPSK teaching waveform: 20 kbit/s information, 10 ksymbol/s, RRC roll-off 0.35 and D3 at 80 ksample/s. It is not automatically Wi-Fi, Bluetooth or a permitted mode. G02 adds a separately specified Wi-Fi radio; G03’s cellular option is also incomplete. “F-GLOBAL” is a proposed control strategy awaiting national channel, power, antenna and update-path review.

A defensible preference is to review stable N01/A0 first while the gateway owner resolves A1 and concurrency. An equally defensible alternative may prioritize a gateway market with a strong commercial need, provided its unresolved hardware and sample work stays visible.

Go deeperInspect the inherited configuration boundary

SKU set: N01, N02, N03, G01, G02, G03. Antennas: SYN-A0-v1, SYN-A1-v1. Supplies: SYN-P0-v1, SYN-P1-v1, SYN-P2-v1. Region images: F-EU, F-CH, F-GB, F-NA. G02-NA-MA / M-A hardware 1 / H0 F1 A0 versus H1 F2 A1, SYN-ENC-NA-v1, USB supply and 1 dB feed remain separate 09.4 studies.

id: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1
parentId: SYN-P09-M01-MANIFEST-v1
scenario: teaching-node-v1
sku: N01
hardware: SYN-HW-N01-v1
firmware: SYN-FW-N01-F-EU-v1
region: F-EU
radios: Node: generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35, 80 ksample/s D3; no standardized mode inferred.
mode: node-TX
concurrent: false
antenna: A0
antennaVersion: SYN-A0-v1
cable: Internal fixed feed SYN-FEED-v1
enclosure: SYN-ENC-N01-v1
supply: P0
supplyVersion: SYN-P0-v1
installation: SYN-INSTALL-v1: indoor fixed bracket proposed; separation, mobility during service and outdoor use unresolved
user: SYN-USER-v1: technician installer and general end user proposed; access/service conditions unresolved
environment: 25 °C bench identity only; operational temperature, humidity and foreseeable environment unresolved
sample: SYN-SAMPLE-N01-01
regionControl: SYN-REGION-v1: four build images exist; signed configuration, recovery and forbidden-state reachability evidence unknown
testImageRelation: SYN-TEST-v1 mapped to production image ID; radio-state equivalence and command limits need reviewer evidence

Engineering consequence → record update

Record the chosen tiers and the reasons for them beside the controlled manifest. Do not turn the tier dropdown into an unexplained country score or a hidden task dependency.

03 / 10

A dossier is a set of answerable questions

A country dossier is a chain of answerable questions, with an owner and a source for each answer. Start with territory, activity and date: importing, placing on the market and operating are distinct claims. Next identify the actual product and national operating conditions. Only then select the technical route, standards and methods, evidence providers, documents and responsible actors. Record an unresolved category as unknown rather than forcing a familiar radio name into an annex.

Read the source’s role before its conclusion. Law establishes obligations; a regulator’s workflow explains a process; a standard defines a technical method within its scope; a recognition record identifies a body’s accepted scope; a representative body describes its service. A supplier report documents a particular sample and method. Alliance or operator qualification belongs in its own lane. None of these roles can be substituted solely because the issuer’s logo looks authoritative.

Evidence example · an answerable record has a verb and an owner

“Japan certificate needed” leaves the design team guessing. “JP reviewer: identify the current equipment category and registered-body scope for N01/A1 before representative samples are frozen” states the object, unresolved decision and dependency. Record the actual text read, language, version, activity date and next question beside it.

The source chain and the evidence it must preserve
Question	Record before moving on
Which obligation applies?	Territory, product category, activity, operative source and applicable date; reviewed rationale for any exemption.
What does the test answer?	Method edition, configuration, quantity, unit, detector, bandwidth, distance, reference plane, statistic and decision/uncertainty basis.
Who may provide and use it?	Lab competence, required recognition, receiving acceptance basis, actor and named human scope review.
What changes the answer?	Source transition, firmware/antenna/concurrency change, sample revision, local document or body-scope change.

The actual-source dossiers in sections 5–8 use research accessed on 2026-09-09. The planner’s SYN- records use a frozen evaluation of 2026-09-08 and internal review due through 2026-12-07. The following day means “recheck this source snapshot,” not “the report legally expired.” Publication, entry into force, application, transition end, access and review remain separate fields.

Engineering consequence → record update

Create p09-m05-expansion-register-v1 under p09-compliance-register-v1. Retain parent IDs and unknown activity dates. A source card with unread operative text cannot support a completed product classification.

04 / 10

Reuse evidence one field at a time

Begin reuse with the underlying data. The measurement traceability lesson separates a raw observation from a derived result and its method. A formal report adds a controlled sample, procedure and interpretation. A laboratory’s competence record and its receiving recognition are further objects. A conformity decision and product authorization are further objects again. Keep their identifiers; a new analysis does not rewrite the original report.

The planner compares eleven required dimensions for one report and one receiving requirement. Identity includes hardware and firmware. Mode includes concurrency. Physical scope includes antenna, feed, enclosure, supply and installation. Exact method and measurement-contract fields lead to the decision/uncertainty basis. Competence, recognition, evidence timing, receiving acceptance and human scope review complete the chain. No weighted score can hide a missing required dimension.

Think about itThe method matches and the lab is accredited. Its receiving recognition scope is missing. What should R3 show?

Answer

Inspect. Accreditation does not supply the missing recognition record. Obtain the lab’s exact required scope and dates, then confirm the receiving basis. The U.S. rules themselves distinguish accreditation and recognition; an MRA also has a defined phase and scope rather than a universal approval-transfer promise. [US] [KR5]

Evidence example · same family, unequal versions, different conclusions

R2 → BR has an explicitly incompatible method edition and no bridge. R6 → JP has unequal version strings but an exact reviewed bridge, with receiving acceptance and human review supplied in the exercise. R5 → AU has only a proposed bridge. These are three different documentary states; sorting version numbers cannot decide among them.

An equivalence bridge names the source and target, dimension, report, market, configurations, applicable interval and reviewer. It is directional: X → Y does not establish Y → X, and X → Y plus Y → Z does not establish X → Z. Its limitation follows the result. It may justify a defined analysis or supplementary plan; it does not transfer a grant.

Go deeperThe exact precedence rule

Invalid IDs, contradictory scope or malformed dates stop evaluation. For valid input, any incompatible dimension gives “not reusable on the supplied basis,” while preserving every other gap. Otherwise unknown, unread or overdue support gives “inspect.” Otherwise a proposed bridge gives “conditional proposal.” Only supported or explicitly reviewed not-applicable dimensions, with receiving acceptance and human review supplied, give “reuse rationale recorded.” Acceptance and human review cannot be waived as not applicable.

Engineering consequence → record update

Record the precise receiving requirement and every dimension’s evidence. If all candidates are unsupported, retain “no supported reuse candidate”; the least incomplete report is not an acceptable substitute.

05 / 10

Australia: supplier evidence and national conditions

Australia illustrates why supplier evidence and radio operation need separate lines. ACMA’s five-step workflow moves from applicable rules to evidence, records, registration and marking. The duties depend on the product. Its rule guidance separates radio, EMC, electromagnetic energy and telecommunications questions; the national LIPD conditions are another necessary source for a candidate device. [AU1] [AU2] [AU7]

For N01, the next useful decision is the actual equipment/compliance category and licence item. ACMA’s evidence guidance differentiates compliance levels and test-provider requirements. A foreign report can only help after the selected method, evidence route and required recognition are understood. The document does not make an accreditation badge sufficient for every receiving requirement. [AU3]

Evidence example · the label designer is waiting for an engineering decision

The artist can draft space for product identification. The supplier owner still needs the applicable registration and record route, while the RF lead needs national antenna and power conditions. Finishing artwork does not resolve those dependencies. Keep the signatory, records, marking eligibility and electrical-safety scope as answerable questions. [AU4] [AU5] [AU6]

Australia · actual-source dossier

P09-M05-AU-v1 · proposed import, placing on the market and intended operation. Actual activity dates are not supplied. Candidate: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1; gateway variants remain separate. Source access and editorial review 2026-09-09; internal recheck due through 2026-12-08.

Authority and legal source: ACMA; Radiocommunications Act framework, General Equipment Rules 2021 and relevant national operating licence. Guidance identifies the source chain; selected operative provisions are not yet resolved.
Actual product / category question: N01 generic telemetry transmitter is the candidate. Its actual equipment and compliance level are unresolved. Wi-Fi G02 and cellular G03 need separate category/function reviews.
National spectrum and use conditions: Review a specific LIPD Class Licence 2025 item and all associated conditions. No national power, bandwidth, antenna, duty-cycle or use permission is assigned from 2.450 GHz alone.
Route / body: Trace the applicable supplier evidence, declaration, registration and marking duties. RCM is an outcome of applicable obligations; it is not a worldwide transmitter certificate.
Method, edition and acceptance basis: Determine the actual Schedule 5 / product technical standards, editions, compliance level and any recognition arrangement. AU3 describes conditional evidence routes, not blanket foreign-report acceptance.
Exposure and other requirement families: Keep radio spectrum, EMC, EME and any telecommunications obligations separate. Determine electrical safety scheme applicability for P1/P2 supplies; no reviewed exemption is recorded.
Samples, reports and laboratory scope: Define representative N01 and changed-antenna/gateway configurations. Laboratory competence and, where required, accreditation/recognition must cover the selected method. No mandatory local test or sample count is assumed.
Actor and responsibility: Name the responsible supplier and any agency arrangement. Supplier registration and electrical safety scheme roles require their own applicability checks.
Documents, language and marking: Identify declaration and technical records, English documentation needs, retention conditions, model identification and eligible RCM/e-label presentation. Artwork follows the rule and actor review.
Factory, surveillance, renewal and changes: Review material antenna, firmware, enclosure and supply changes against the evidence. Factory audit, surveillance or renewal is not asserted universally; each duty needs a cited applicable basis or reviewed non-applicability.
Configuration / sequence threat: A national operating condition could invalidate the unreviewed global firmware hypothesis or require antenna/power restrictions.
Next specialist question: Which exact licence item, technical standard and supplier role cover N01 with A1, and what prevents an unsupported firmware region or antenna from being selected?

Owner: AU jurisdiction specialist + RF/firmware lead. Sources: [AU1] [AU2] [AU3] [AU4] [AU5] [AU6] [AU7] [AU8] . Each source’s read scope and dates are retained in the references; no completed national route is asserted.

Common misconceptionOnly the label changes when a product enters another market.

National operating conditions, responsible roles and configuration evidence may change the product or its controls. ACMA also calls for review of product changes and supporting records. [AU8]

Engineering consequence → record update

Keep A1 and global firmware as explicit freeze risks in P09-M05-AU-v1. Assign the supplier/label package and the national RF-condition review to their actual owners.

06 / 10

Brazil: separate technical route and current process

Brazil’s technical and administrative questions have separate sources. Anatel Resolution 715 structures conformity certification, including OCD roles and different certification models, and homologation. A product-specific technical act supplies the applicable technical requirements. The restricted-radiation act is a candidate to investigate for N01, not an automatic classification of the teaching waveform. [BR1] [BR3]

The updated Certifica notice is time-sensitive process evidence. It states that the described procedures move to Certifica from 2026-09-08, that SCH stops new requests, and that specified own-use processes temporarily remain in SEI. It explicitly says the certification and homologation rules do not change. It does not settle the handling of every already-pending SCH filing. [BR2]

Think about itThe submission portal changes. Has the existing RF evidence become technically obsolete?

Answer

The notice alone supports no such conclusion. Record the process change and its scope. Separately check whether a technical act, method, configuration or acceptance rule changed. The document owner should ask what happens to the specific pending filing rather than assume it must be migrated or resubmitted.

Evidence example · two dates, two owners

A fictional dossier was prepared before the portal change but has no real submission. The process owner records the current new-request route and asks about pending cases. The method reviewer retains the exact act/method version and checks the technical basis independently. The schedule may need document work even when no new RF test is justified.

Brazil · actual-source dossier

P09-M05-BR-v1 · proposed import, placing on the market and intended operation. Actual activity dates are not supplied. Candidate: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1; gateway variants remain separate. Source access and editorial review 2026-09-09; internal recheck due through 2026-12-08.

Authority and legal source: Anatel; Resolution 715/2019 as amended. Product-specific technical acts and the actual equipment category remain necessary.
Actual product / category question: Assess whether N01 belongs to the restricted-radiation equipment scope of Act 14448/2017 as amended. G02/G03 radio functions and concurrency are separate facts; the generic waveform is not a named technology category.
National spectrum and use conditions: Select current national technical clauses for the actual transmitter. No allowed channel, output power, antenna condition or operating entitlement has been inferred from the candidate act.
Route / body: Distinguish technical conformity certification by an OCD where that model applies from Anatel homologation. Resolve the product-specific certification model before assigning recurring duties.
Method, edition and acceptance basis: Map current technical act clauses, method versions, report acceptance and lab/body scope. R2’s fictional method conflict says nothing about an actual Brazilian test report.
Exposure and other requirement families: Open spectrum, EMC, exposure, safety and any additional telecom requirements against the actual product and intended activity; do not collapse all families into homologation paperwork.
Samples, reports and laboratory scope: Ask the scoped OCD/evidence reviewer which variants, antenna modes, samples, lab route and manufacturing information this category needs. Local testing and sample quantities remain unassigned.
Actor and responsibility: Name the applicant/responsible local role and the selected OCD only after checking category and scope. A portal account is not a technical certification decision.
Documents, language and marking: Confirm Portuguese documentation, declarations, reports, model identity and identification/label format. The 2026-09-08 notice changes the described submission path; pending SCH filings require an explicit status check.
Factory, surveillance, renewal and changes: Resolution 715 distinguishes certification models, periodic evaluation and change review. Determine applicable maintenance, manufacturing-quality evaluation and identification duties; do not invent a universal renewal interval.
Configuration / sequence threat: A changed A1 antenna or G02 simultaneous state may expand samples and evaluation. A pending filing’s administrative path could change document dependencies without changing RF evidence.
Next specialist question: Which current product act and OCD scope cover this exact configuration, and what happens to our hypothetical pending SCH filing after 2026-09-08?

Owner: BR jurisdiction specialist + process/document owner. Sources: [BR1] [BR2] [BR3] . Each source’s read scope and dates are retained in the references; no completed national route is asserted.

Engineering consequence → record update

Keep the Certifica process notice separate from the technical-act row. Let the applicable certification model determine any maintenance or manufacturing review; do not insert a universal audit or renewal task.

07 / 10

Japan: begin with the equipment category

For Japan, the first question is the current equipment category. The e-Gov source exposed current-version metadata dated 2026-07-30, but the operative clauses were not retrieved in this review. The available Ministry of Justice English translation reflects a 2013 amendment. It is useful for understanding the distinction between certification routes; it cannot establish today’s category or transition conditions. [JP1] [JP2]

TELEC’s service page describes test certification and construction-design certification, with application and technical material for its services. This helps the engineer anticipate a coherent submission package. The selected body’s current registration, equipment scope and the actual MIC legal/method chain still need verification. The MIC radio-site access attempt returned an official error page, which remains a source gap. [JP3] [JP4]

Evidence example · a service checklist is useful before it is sufficient

The product owner gathers the block diagram, antenna description, photos and construction controls. The Japanese-source reviewer must first confirm which current category and route these documents support. If A1 or a software-selectable mode changes that category’s conditions, a polished package around A0 will not represent production.

Japan · actual-source dossier

P09-M05-JP-v1 · proposed import, placing on the market and intended operation. Actual activity dates are not supplied. Candidate: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1; gateway variants remain separate. Source access and editorial review 2026-09-09; internal recheck due through 2026-12-08.

Authority and legal source: MIC / Radio Act and the specified radio-equipment certification ordinance. Current e-Gov version metadata was retrieved; operative category and transition clauses still need review.
Actual product / category question: Identify the actual specified radio-equipment category from current Japanese text. Neither the 2013 English translation nor a TELEC service description chooses N01’s category.
National spectrum and use conditions: Review national frequency, emission, antenna, power and use conditions for the identified category. Station licensing or other operating obligations remain separate questions where relevant.
Route / body: Evaluate the appropriate technical certification / construction-design route and the selected registered body’s current equipment scope. Representative service instructions are not the legal scope decision.
Method, edition and acceptance basis: Resolve current MIC method notices and editions, lab/report acceptance, body recognition and any scoped alternative method bridge. R3 intentionally leaves recognition unknown.
Exposure and other requirement families: Assess radio technical, exposure, EMC, safety and any relevant terminal/network obligations individually. G03 cellular network access and industry/operator acceptance remain separate from radio authorization.
Samples, reports and laboratory scope: TELEC describes application specifications, diagrams, photographs, specimen/data paths and construction-conformance verification material. Confirm the actual product route and body requirements before selecting samples.
Actor and responsibility: Assign the manufacturer/applicant, authorized contact and registered-body review roles for the chosen route. The lesson has not verified a current body listing for this exact equipment category.
Documents, language and marking: Confirm Japanese application/technical material, labels or permitted electronic identification, design consistency and required records from the actual route. Do not treat the historical English translation as current instructions.
Factory, surveillance, renewal and changes: Ask what construction-design controls, changes, continuing conformity, records and any required follow-up apply. No universal factory audit or certificate expiry is assigned.
Configuration / sequence threat: A category-specific antenna or software-control requirement could force a regional image or hardware variant before samples can be frozen.
Next specialist question: Which current Japanese category and registered-body scope cover N01/A1, and which design or software controls would make the submitted sample representative of production?

Owner: JP Japanese-source reviewer + configuration owner. Sources: [JP1] [JP2] [JP3] [JP4] . Each source’s read scope and dates are retained in the references; no completed national route is asserted.

Engineering consequence → record update

Put the current category, body scope and method retrieval before sample freeze. Keep station/operating and terminal/network questions separate where relevant; a radio-equipment review does not silently close them.

08 / 10

South Korea: read the actual assessment category

South Korea provides a concrete reason to preserve source language and version. RRA’s Korean overview lists four assessment categories under Article 58-2; its English overview lists three. The Korean page includes self-confirmation, while the English list does not. This observation identifies a source discrepancy. It does not establish which category N01 or G02 belongs to. The English descriptions here are educational paraphrases, not certified legal translations. [KR1] [KR2]

The notice records identify conformity-assessment notice 2026-4 dated 2026-07-24 and laboratory designation/management notice 2026-5 dated 2026-08-21. Their metadata was read; their attached operative text was not. Ask a Korean-source reviewer to resolve the actual annex entry, transition and laboratory scope. “Wi-Fi” or “accredited” cannot fill an unread annex cell. [KR3] [KR4]

Evidence example · recognition has a scope, not just a logo

A proposed foreign lab provides a competence record. The dossier still needs the relevant recognition mechanism, parties, phase, dates and equipment/method scope. RRA’s MRA explanation distinguishes testing/laboratory recognition from certification-body/certificate recognition. It does not supply a selected bilateral acceptance decision for this product. [KR5]

South Korea · actual-source dossier

P09-M05-KR-v1 · proposed import, placing on the market and intended operation. Actual activity dates are not supplied. Candidate: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1; gateway variants remain separate. Source access and editorial review 2026-09-09; internal recheck due through 2026-12-08.

Authority and legal source: RRA; Radio Waves Act Article 58-2 orientation and conformity-assessment notice 2026-4. Current Korean annex/transition text is not yet read.
Actual product / category question: The Korean overview lists certification, registration, self-confirmation and interim certification; the English overview lists three. Resolve the applicable annex for N01 and each gateway radio function from Korean sources.
National spectrum and use conditions: Identify the actual national technical criteria, permitted modes, channels, antenna/power conditions and installation restrictions. A shared carrier or a Wi-Fi name cannot answer these questions.
Route / body: Select the category and its evidence/declaration/registration or certification procedure from the current Korean text. Do not choose self-confirmation merely because it appears on the newer overview.
Method, edition and acceptance basis: Read notice 2026-4 and lab designation notice 2026-5, then verify method/edition, test body scope, any MRA parties/phase/dates and report acceptance. The attachments remain a named source gap.
Exposure and other requirement families: Review spectrum, EMC, exposure, safety and any terminal/service obligations separately. A category decision is not an automatic conclusion for every requirement family.
Samples, reports and laboratory scope: Resolve representative samples and designated/recognized laboratory requirements for the actual category. A foreign accreditation badge alone cannot close the recognition question.
Actor and responsibility: Identify the applicant, local representative or responsible party where required by the selected procedure. Assign Korean-source translation and evidence review owners before finalizing the package.
Documents, language and marking: Confirm Korean documentation, product/model identity, conformity record and marking/e-label conditions from the operative procedure; no generic worldwide label template is assumed.
Factory, surveillance, renewal and changes: Identify applicable change notification, continuing conformity, sample follow-up, factory or renewal provisions in the actual category. Unread text is unknown, not not-applicable.
Configuration / sequence threat: G02’s concurrent radios and changed A1/feed may require a different representative configuration and additional evidence before external review can start.
Next specialist question: Which Korean annex entry covers G02 with simultaneous transmitters and A1, and does that scope accept the proposed laboratory and single-radio source report?

Owner: KR Korean-source reviewer + RF test lead. Sources: [KR1] [KR2] [KR3] [KR4] [KR5] . Each source’s read scope and dates are retained in the references; no completed national route is asserted.

Engineering consequence → record update

Keep R4’s antenna and concurrency conflicts visible while the Korean-source owner resolves the actual category. Neither a language shortcut nor one repaired dimension closes the other obligations.

09 / 10

Local dependencies determine the plan

Local dependencies can change the engineering sequence. Samples need a controlled configuration. A selected body may need a particular technical package. A responsible actor may need reviewed translations and product identification before a filing can proceed. Factory, surveillance, renewal and change duties must come from the applicable route; do not assign every country the same tasks. The pre-compliance discipline remains useful for design decisions while formal acceptance remains open.

Use a small dependency model to expose the difference between doing work faster and completing the package earlier. Each task below is required; time zero is a fictional scenario start. Durations are elapsed teaching work units, not days, lab quotations or country lead times. Unlimited parallel resources are assumed. Shared people/equipment, rework, holidays, queues, fees and uncertain external review are outside this model.

Baseline only: D joins methods and samples; F joins evaluation and the actor/document package. The task table is the full dependency and timing equivalent. Custom planner diagrams below are computed from the committed state.

The forward pass takes each task’s earliest start as the largest predecessor finish, then adds its duration. Project completion is the largest sink finish, including disconnected required work. The backward pass sets each sink’s latest finish to that completion and works backwards through the smallest successor latest start. Total float is latest start minus earliest start. A critical path is a complete tight chain of zero-float tasks; ties can produce several.

Independent baseline · exact teaching units
Task / required predecessors	Duration	ES	EF	LS	LF	Total float
A · Freeze scope and configuration questionsRequires none	2	0	2	0	2	0
B · Compare methods and evidenceRequires A	3	2	5	3	6	1
C · Prepare representative samplesRequires A	4	2	6	2	6	0
D · Run the planned supplementary evaluationRequires B, C	5	6	11	6	11	0
E · Resolve the local-actor/document packageRequires A	2	2	4	9	11	7
F · Complete the external review packageRequires D, E	6	11	17	11	17	0
G · Reconcile records and controlled release proposalRequires F	2	17	19	17	19	0

Think about itThe actor/document task E takes two units. If it is expedited to zero, does the project finish earlier?

Answer

No. D finishes at 11, so F must still wait until 11 even when E finishes at 2. The project stays at 19. E’s total float increases from 7 to 9; the critical chain remains A → C → D → F → G. The actor evidence hold can remain open regardless of the numerical duration.

Evidence example · a one-unit delay changes the critical chain

Baseline B finishes at 5 and has one unit of float before D’s start at 6. Change B’s duration from 3 to 5: B finishes at 7, D at 12, F at 18 and G at 20. A → B → D → F → G becomes critical; C now has one unit of float. The relevant question is which predecessor limits the join.

Go deeperComplete worked counterexamples, including tied paths

Expedite E · duration zero

Completion 19 teaching units. Critical paths: A → C → D → F → G.

expedite · full timing
Task / required predecessors	Duration	ES	EF	LS	LF	Total float
A · Freeze scope and configuration questionsRequires none	2	0	2	0	2	0
B · Compare methods and evidenceRequires A	3	2	5	3	6	1
C · Prepare representative samplesRequires A	4	2	6	2	6	0
D · Run the planned supplementary evaluationRequires B, C	5	6	11	6	11	0
E · Resolve the local-actor/document packageRequires A	0	2	2	11	11	9
F · Complete the external review packageRequires D, E	6	11	17	11	17	0
G · Reconcile records and controlled release proposalRequires F	2	17	19	17	19	0

Delay B · duration five

Completion 20 teaching units. Critical paths: A → B → D → F → G.

delay · full timing
Task / required predecessors	Duration	ES	EF	LS	LF	Total float
A · Freeze scope and configuration questionsRequires none	2	0	2	0	2	0
B · Compare methods and evidenceRequires A	5	2	7	2	7	0
C · Prepare representative samplesRequires A	4	2	6	3	7	1
D · Run the planned supplementary evaluationRequires B, C	5	7	12	7	12	0
E · Resolve the local-actor/document packageRequires A	2	2	4	10	12	8
F · Complete the external review packageRequires D, E	6	12	18	12	18	0
G · Reconcile records and controlled release proposalRequires F	2	18	20	18	20	0

Bounded C / D / F durations

Completion [16, 26] teaching units. Lower corner paths: A → B → D → F → G; A → C → D → F → G. Upper corner: A → C → D → F → G.

bounded · lower corner
Task / required predecessors	Duration	ES	EF	LS	LF	Total float
A · Freeze scope and configuration questionsRequires none	2	0	2	0	2	0
B · Compare methods and evidenceRequires A	3	2	5	2	5	0
C · Prepare representative samplesRequires A	[3, 6]	2	5	2	5	0
D · Run the planned supplementary evaluationRequires B, C	[4, 7]	5	9	5	9	0
E · Resolve the local-actor/document packageRequires A	2	2	4	7	9	5
F · Complete the external review packageRequires D, E	[5, 9]	9	14	9	14	0
G · Reconcile records and controlled release proposalRequires F	2	14	16	14	16	0

Bounded example · upper corner
Task / required predecessors	Duration	ES	EF	LS	LF	Total float
A · Freeze scope and configuration questionsRequires none	2	0	2	0	2	0
B · Compare methods and evidenceRequires A	3	2	5	5	8	3
C · Prepare representative samplesRequires A	[3, 6]	2	8	2	8	0
D · Run the planned supplementary evaluationRequires B, C	[4, 7]	8	15	8	15	0
E · Resolve the local-actor/document packageRequires A	2	2	4	13	15	11
F · Complete the external review packageRequires D, E	[5, 9]	15	24	15	24	0
G · Reconcile records and controlled release proposalRequires F	2	24	26	24	26	0

With C ∈ [3,6], D ∈ [4,7] and F ∈ [5,9], the monotone fixed graph gives completion [16,26]. At the lower corner B and C tie, so both A → B → D → F → G and A → C → D → F → G are critical. These endpoints are scenario bounds, not probabilities. With F unknown, upstream times and F’s start at 11 remain known; its finish and project completion do not. Adding G as A’s predecessor creates a cycle and no valid schedule.

Engineering consequence → record update

Ask for the actual dependency and its owner before requesting a date. Record unresolved external work as unknown; do not substitute zero or call a computed finish release readiness.

10 / 10

Defend the phased expansion dossier

Use the evidence bench to defend a phased expansion brief. Begin with R3’s recognition gap, then compare the incompatible R2 method with R6’s reviewed unequal-version bridge. Inspect R5’s pending bridge before recording any support. Next expedite E, delay B and load the bounded scenario. Predict each result before comparing it. Reset restores the complete canonical package, including dates and review metadata.

The six synthetic comparisons start at 2 reuse rationales recorded, 1 conditional proposal, 2 not reusable on the supplied basis and 1 inspect. Reviewing R5’s bridge changes only that comparison if every other dimension remains supported. R1’s overdue source becomes inspect. All unsupported candidates remain unsupported; the model never selects a least-incomplete winner.

Evidence example · a narrow repair preserves the real queue

In the exercise, change only R5’s method state to supported and compare. That records a fictional reviewed bridge for its exact pair. R2’s method conflict, R3’s recognition question and R4’s configuration conflicts survive. Then set R5’s receiving acceptance to unknown: the reviewed bridge remains useful but the comparison returns to inspect.

Interactive evidence bench · synthetic exercise

Market Dossier & Reuse Planner

Predict a result, change one fact, then compare. The real country dossiers above remain separate. No report uploads, network requests or saved project data.

Interactive editing needs JavaScript. The complete baseline, all dimensions, schedule, holds and worked alternatives are available below and in print. Open the native disclosures to inspect evidence.

Review a bounded fictional package

Complete scenario presetLoading a preset commits its entire defined state, including the intentionally invalid cycle example.

Dossier focus (view only)Focus AU; all reports and obligations remain below. Read the actual AU dossier.

AU planning tier (declared preference)Does not change task dependencies or close a hold.

Evaluation date (YYYY-MM-DD)

One directed report comparison

Report / receiving target

Required comparison dimensionSelected: Laboratory recognition for required scope. Draft state: supported.

Synthetic review stateManual support creates a named fictional review overlay. An unequal pair also requires a scoped bridge. Acceptance and human review cannot be marked not applicable.

Source review caseCurrentness is evaluated against the entered as-of date and due date.

Internal source review due through (YYYY-MM-DD)

Receiving acceptance evidenceA real receiving decision is never generated here.

Task durations · teaching work units

Integer 0–30, step 1. Interval presets use two comma-separated integer endpoints. Unknown is explicit; dependencies are preserved from the selected preset.

A · Freeze scope and configuration questions Duration unknownRequires none

B · Compare methods and evidence Duration unknownRequires A

C · Prepare representative samples Duration unknownRequires A

D · Run the planned supplementary evaluation Duration unknownRequires B, C

E · Resolve the local-actor/document package Duration unknownRequires A

F · Complete the external review package Duration unknownRequires D, E

G · Reconcile records and controlled release proposal Duration unknownRequires F

Committed evidence review

Baseline · six synthetic comparisons · evaluated as of 2026-09-08
market-dossier-reuse-planner/2.0 · p09-m05-reuse-rules-v1 · p09-m05-dossiers-v1 · p09-m05-schedule-v1

2 reuse rationale recorded · 1 conditional proposal · 2 not reusable on the supplied basis · 1 inspect

These statuses measure the completeness of fictional review metadata. They do not decide national compliance, accept a real report or transfer an authorization. Market tiers are preferences: AU: First review; BR: Parallel review; JP: Parallel review; KR: Deferred review. All four markets and their holds remain in scope.

R1 → AU reuse rationale recorded

SYN-REPORT-R1-v1 → SYN-REQUIREMENT-AU-R1-v1
Configuration: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1 → SYN-MAN-N01-A0-P0-F-EU-node-TX-v1

identity: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
mode: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
physical: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
method: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
measurement: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
decision: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
competence: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
recognition: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
timing: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
acceptance: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
human: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.

Inspect all 11 dimensions, evidence, reviewers and bridges for R1

R1 · complete directed comparison
Dimension / state	Source → receiving requirement	Evidence / scope review
Product / hardware / firmware identitysupported	From: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1 To: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-identity-v1` Fictional evidence reviewer · 2026-09-08
Radio mode and concurrencysupported	From: Generic QPSK node-TX; no second radio To: Generic QPSK node-TX; no second radio	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-mode-v1` Fictional evidence reviewer · 2026-09-08
Antenna / feed / enclosure / supply / installationsupported	From: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1 To: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-physical-v1` Fictional evidence reviewer · 2026-09-08
Exact method and editionsupported	From: SYN-METHOD-FAMILY-v1 To: SYN-METHOD-FAMILY-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-method-v1` Fictional evidence reviewer · 2026-09-08
Frequency / bandwidth / detector / distance / plane / statisticsupported	From: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned To: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-measurement-v1` Fictional evidence reviewer · 2026-09-08
Limit, uncertainty and decision basissupported	From: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit To: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-decision-v1` Fictional evidence reviewer · 2026-09-08
Laboratory competencesupported	From: SYN-LAB-COMPETENCE-v1 for the declared method To: SYN-LAB-COMPETENCE-v1 for the declared method	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-competence-v1` Fictional evidence reviewer · 2026-09-08
Laboratory recognition for required scopesupported	From: SYN-LAB-RECOGNITION-v1 for this receiving requirement To: SYN-LAB-RECOGNITION-v1 for this receiving requirement	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-recognition-v1` Fictional evidence reviewer · 2026-09-08
Evidence date and transition supportsupported	From: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval To: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-timing-v1` Fictional evidence reviewer · 2026-09-08
Receiving requirement acceptance basissupported	From: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only To: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-acceptance-v1` Fictional evidence reviewer · 2026-09-08
Human scope and reuse reviewsupported	From: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer To: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R1-human-v1` Fictional evidence reviewer · 2026-09-08

Source review: current. Synthetic publication 2026-08-01; access 2026-09-08; review 2026-09-08; due through 2026-12-07. Entry into force unspecified; application unspecified; transition end unspecified. The review due date is an internal teaching trigger, not a legal expiry.

Separate source-market authorization lane: No real source-market authorization supplied. A report is a separate object; target product authorization remains unresolved.

R2 → BR not reusable on the supplied basis

SYN-REPORT-R2-v1 → SYN-REQUIREMENT-BR-R2-v1
Configuration: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1 → SYN-MAN-N01-A0-P0-F-EU-node-TX-v1

identity: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
mode: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
physical: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
method: incompatible — Same method family, explicitly incompatible edition; no scoped bridge supplied.
measurement: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
decision: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
competence: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
recognition: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
timing: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
acceptance: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
human: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.

Inspect all 11 dimensions, evidence, reviewers and bridges for R2

R2 · complete directed comparison
Dimension / state	Source → receiving requirement	Evidence / scope review
Product / hardware / firmware identitysupported	From: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1 To: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-identity-v1` Fictional evidence reviewer · 2026-09-08
Radio mode and concurrencysupported	From: Generic QPSK node-TX; no second radio To: Generic QPSK node-TX; no second radio	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-mode-v1` Fictional evidence reviewer · 2026-09-08
Antenna / feed / enclosure / supply / installationsupported	From: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1 To: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-physical-v1` Fictional evidence reviewer · 2026-09-08
Exact method and editionincompatible	From: SYN-METHOD-FAMILY-v1 To: SYN-METHOD-FAMILY-v2	Same method family, explicitly incompatible edition; no scoped bridge supplied. `SYN-R2-method-v1` Fictional evidence reviewer · 2026-09-08
Frequency / bandwidth / detector / distance / plane / statisticsupported	From: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned To: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-measurement-v1` Fictional evidence reviewer · 2026-09-08
Limit, uncertainty and decision basissupported	From: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit To: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-decision-v1` Fictional evidence reviewer · 2026-09-08
Laboratory competencesupported	From: SYN-LAB-COMPETENCE-v1 for the declared method To: SYN-LAB-COMPETENCE-v1 for the declared method	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-competence-v1` Fictional evidence reviewer · 2026-09-08
Laboratory recognition for required scopesupported	From: SYN-LAB-RECOGNITION-v1 for this receiving requirement To: SYN-LAB-RECOGNITION-v1 for this receiving requirement	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-recognition-v1` Fictional evidence reviewer · 2026-09-08
Evidence date and transition supportsupported	From: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval To: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-timing-v1` Fictional evidence reviewer · 2026-09-08
Receiving requirement acceptance basissupported	From: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only To: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-acceptance-v1` Fictional evidence reviewer · 2026-09-08
Human scope and reuse reviewsupported	From: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer To: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R2-human-v1` Fictional evidence reviewer · 2026-09-08

Separate source-market authorization lane: No real source-market authorization supplied. A report is a separate object; target product authorization remains unresolved.

R3 → JP inspect

SYN-REPORT-R3-v1 → SYN-REQUIREMENT-JP-R3-v1
Configuration: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1 → SYN-MAN-N01-A0-P0-F-EU-node-TX-v1

identity: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
mode: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
physical: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
method: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
measurement: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
decision: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
competence: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
recognition: unknown — A competence/accreditation record is present; receiving recognition scope is absent. Obtain the named recognition scope and dates.
timing: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
acceptance: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
human: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.

Inspect all 11 dimensions, evidence, reviewers and bridges for R3

R3 · complete directed comparison
Dimension / state	Source → receiving requirement	Evidence / scope review
Product / hardware / firmware identitysupported	From: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1 To: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-identity-v1` Fictional evidence reviewer · 2026-09-08
Radio mode and concurrencysupported	From: Generic QPSK node-TX; no second radio To: Generic QPSK node-TX; no second radio	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-mode-v1` Fictional evidence reviewer · 2026-09-08
Antenna / feed / enclosure / supply / installationsupported	From: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1 To: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-physical-v1` Fictional evidence reviewer · 2026-09-08
Exact method and editionsupported	From: SYN-METHOD-FAMILY-v1 To: SYN-METHOD-FAMILY-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-method-v1` Fictional evidence reviewer · 2026-09-08
Frequency / bandwidth / detector / distance / plane / statisticsupported	From: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned To: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-measurement-v1` Fictional evidence reviewer · 2026-09-08
Limit, uncertainty and decision basissupported	From: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit To: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-decision-v1` Fictional evidence reviewer · 2026-09-08
Laboratory competencesupported	From: SYN-LAB-COMPETENCE-v1 for the declared method To: SYN-LAB-COMPETENCE-v1 for the declared method	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-competence-v1` Fictional evidence reviewer · 2026-09-08
Laboratory recognition for required scopeunknown	From: SYN-LAB-RECOGNITION-v1 for this receiving requirement To: Required recognition for SYN-REQUIREMENT-JP-R3-v1	A competence/accreditation record is present; receiving recognition scope is absent. Obtain the named recognition scope and dates. `SYN-R3-recognition-v1` Fictional evidence reviewer · 2026-09-08
Evidence date and transition supportsupported	From: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval To: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-timing-v1` Fictional evidence reviewer · 2026-09-08
Receiving requirement acceptance basissupported	From: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only To: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-acceptance-v1` Fictional evidence reviewer · 2026-09-08
Human scope and reuse reviewsupported	From: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer To: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R3-human-v1` Fictional evidence reviewer · 2026-09-08

Separate source-market authorization lane: No real source-market authorization supplied. A report is a separate object; target product authorization remains unresolved.

R4 → KR not reusable on the supplied basis

SYN-REPORT-R4-v1 → SYN-REQUIREMENT-KR-R4-v1
Configuration: SYN-G02-SINGLE-A0-v1 → SYN-G02-CONCURRENT-A1-v1

identity: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
mode: incompatible — Original single-radio evidence excludes the requested simultaneous state.
physical: incompatible — The changed A1 antenna/feed has no reviewed physical equivalence. Concurrency remains a separate mismatch.
method: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
measurement: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
decision: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
competence: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
recognition: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
timing: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
acceptance: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
human: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.

Inspect all 11 dimensions, evidence, reviewers and bridges for R4

R4 · complete directed comparison
Dimension / state	Source → receiving requirement	Evidence / scope review
Product / hardware / firmware identitysupported	From: G02 / SYN-HW-G02-v1 / SYN-FW-G02-F-NA-v1 To: G02 / SYN-HW-G02-v1 / SYN-FW-G02-F-NA-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R4-identity-v1` Fictional evidence reviewer · 2026-09-08
Radio mode and concurrencyincompatible	From: Single node transmitter To: Concurrent Wi-Fi + node transmitter	Original single-radio evidence excludes the requested simultaneous state. `SYN-R4-mode-v1` Fictional evidence reviewer · 2026-09-08
Antenna / feed / enclosure / supply / installationincompatible	From: A0 / SYN-FEED-v1 / SYN-ENC-G02-v1 / SYN-P2-v1 / SYN-INSTALL-v1 To: A1 / SYN-COAX-v1 / SYN-ENC-G02-v1 / SYN-P2-v1 / SYN-INSTALL-v1	The changed A1 antenna/feed has no reviewed physical equivalence. Concurrency remains a separate mismatch. `SYN-R4-physical-v1` Fictional evidence reviewer · 2026-09-08
Exact method and editionsupported	From: SYN-METHOD-FAMILY-v1 To: SYN-METHOD-FAMILY-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R4-method-v1` Fictional evidence reviewer · 2026-09-08
Frequency / bandwidth / detector / distance / plane / statisticsupported	From: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned To: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R4-measurement-v1` Fictional evidence reviewer · 2026-09-08
Limit, uncertainty and decision basissupported	From: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit To: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R4-decision-v1` Fictional evidence reviewer · 2026-09-08
Laboratory competencesupported	From: SYN-LAB-COMPETENCE-v1 for the declared method To: SYN-LAB-COMPETENCE-v1 for the declared method	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R4-competence-v1` Fictional evidence reviewer · 2026-09-08
Laboratory recognition for required scopesupported	From: SYN-LAB-RECOGNITION-v1 for this receiving requirement To: SYN-LAB-RECOGNITION-v1 for this receiving requirement	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R4-recognition-v1` Fictional evidence reviewer · 2026-09-08
Evidence date and transition supportsupported	From: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval To: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R4-timing-v1` Fictional evidence reviewer · 2026-09-08
Receiving requirement acceptance basissupported	From: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only To: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R4-acceptance-v1` Fictional evidence reviewer · 2026-09-08
Human scope and reuse reviewsupported	From: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer To: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R4-human-v1` Fictional evidence reviewer · 2026-09-08

Separate source-market authorization lane: No real source-market authorization supplied. A report is a separate object; target product authorization remains unresolved.

R5 → AU conditional proposal

SYN-REPORT-R5-v1 → SYN-REQUIREMENT-AU-R5-v1
Configuration: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1 → SYN-MAN-N01-A0-P0-F-EU-node-TX-v1

identity: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
mode: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
physical: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
method: proposed bridge awaiting review — A named directional method bridge is proposed; review is pending.
measurement: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
decision: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
competence: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
recognition: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
timing: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
acceptance: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
human: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.

Inspect all 11 dimensions, evidence, reviewers and bridges for R5

R5 · complete directed comparison
Dimension / state	Source → receiving requirement	Evidence / scope review
Product / hardware / firmware identitysupported	From: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1 To: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-identity-v1` Fictional evidence reviewer · 2026-09-08
Radio mode and concurrencysupported	From: Generic QPSK node-TX; no second radio To: Generic QPSK node-TX; no second radio	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-mode-v1` Fictional evidence reviewer · 2026-09-08
Antenna / feed / enclosure / supply / installationsupported	From: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1 To: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-physical-v1` Fictional evidence reviewer · 2026-09-08
Exact method and editionproposed bridge awaiting review	From: SYN-METHOD-FAMILY-v1 To: SYN-METHOD-VARIANT-v1	A named directional method bridge is proposed; review is pending. `SYN-R5-method-v1` Fictional evidence reviewer · 2026-09-08 SYN-BRIDGE-R5-method · proposed SYN-REPORT-R5-v1 / AU / method SYN-MAN-N01-A0-P0-F-EU-node-TX-v1 → SYN-MAN-N01-A0-P0-F-EU-node-TX-v1 2026-09-08 through 2026-12-07; Fictional scoped-equivalence reviewer; review pending Only this directed pair and dimension within the named configurations and interval. Supports this synthetic comparison; does not rewrite the original report, establish legal acceptance, reverse direction, chain to another bridge or transfer an authorization.
Frequency / bandwidth / detector / distance / plane / statisticsupported	From: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned To: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-measurement-v1` Fictional evidence reviewer · 2026-09-08
Limit, uncertainty and decision basissupported	From: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit To: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-decision-v1` Fictional evidence reviewer · 2026-09-08
Laboratory competencesupported	From: SYN-LAB-COMPETENCE-v1 for the declared method To: SYN-LAB-COMPETENCE-v1 for the declared method	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-competence-v1` Fictional evidence reviewer · 2026-09-08
Laboratory recognition for required scopesupported	From: SYN-LAB-RECOGNITION-v1 for this receiving requirement To: SYN-LAB-RECOGNITION-v1 for this receiving requirement	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-recognition-v1` Fictional evidence reviewer · 2026-09-08
Evidence date and transition supportsupported	From: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval To: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-timing-v1` Fictional evidence reviewer · 2026-09-08
Receiving requirement acceptance basissupported	From: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only To: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-acceptance-v1` Fictional evidence reviewer · 2026-09-08
Human scope and reuse reviewsupported	From: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer To: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R5-human-v1` Fictional evidence reviewer · 2026-09-08

Bridge limitation: SYN-BRIDGE-R5-method: SYN-METHOD-FAMILY-v1 → SYN-METHOD-VARIANT-v1; Only this directed pair and dimension within the named configurations and interval. Supports this synthetic comparison; does not rewrite the original report, establish legal acceptance, reverse direction, chain to another bridge or transfer an authorization.

Separate source-market authorization lane: No real source-market authorization supplied. A report is a separate object; target product authorization remains unresolved.

R6 → JP reuse rationale recorded

SYN-REPORT-R6-v1 → SYN-REQUIREMENT-JP-R6-v1
Configuration: SYN-MAN-N01-A0-P0-F-EU-node-TX-v1 → SYN-MAN-N01-A0-P0-F-EU-node-TX-v1

identity: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
mode: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
physical: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
method: supported — Unequal method versions have a reviewed compatible bridge for this exact pair; receiving acceptance and human review are also supplied.
measurement: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
decision: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
competence: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
recognition: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
timing: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
acceptance: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.
human: supported — Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement.

Inspect all 11 dimensions, evidence, reviewers and bridges for R6

R6 · complete directed comparison
Dimension / state	Source → receiving requirement	Evidence / scope review
Product / hardware / firmware identitysupported	From: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1 To: N01 / SYN-HW-N01-v1 / SYN-FW-N01-F-EU-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-identity-v1` Fictional evidence reviewer · 2026-09-08
Radio mode and concurrencysupported	From: Generic QPSK node-TX; no second radio To: Generic QPSK node-TX; no second radio	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-mode-v1` Fictional evidence reviewer · 2026-09-08
Antenna / feed / enclosure / supply / installationsupported	From: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1 To: SYN-A0-v1 / SYN-FEED-v1 / SYN-ENC-N01-v1 / SYN-P0-v1 / SYN-INSTALL-v1	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-physical-v1` Fictional evidence reviewer · 2026-09-08
Exact method and editionsupported	From: SYN-METHOD-FAMILY-v1 To: SYN-METHOD-FAMILY-v3	Unequal method versions have a reviewed compatible bridge for this exact pair; receiving acceptance and human review are also supplied. `SYN-R6-method-v1` Fictional evidence reviewer · 2026-09-08 SYN-BRIDGE-R6-method · reviewed SYN-REPORT-R6-v1 / JP / method SYN-MAN-N01-A0-P0-F-EU-node-TX-v1 → SYN-MAN-N01-A0-P0-F-EU-node-TX-v1 2026-09-08 through 2026-12-07; Fictional scoped-equivalence reviewer; review 2026-09-08 Only this directed pair and dimension within the named configurations and interval. Supports this synthetic comparison; does not rewrite the original report, establish legal acceptance, reverse direction, chain to another bridge or transfer an authorization.
Frequency / bandwidth / detector / distance / plane / statisticsupported	From: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned To: SYN-MEASUREMENT-CONTRACT-v1: same frequency, bandwidth, detector, distance, plane and statistic fields; no regulatory values assigned	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-measurement-v1` Fictional evidence reviewer · 2026-09-08
Limit, uncertainty and decision basissupported	From: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit To: SYN-DECISION-CONTRACT-v1: same declared limit/uncertainty basis; no measured pass or real limit	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-decision-v1` Fictional evidence reviewer · 2026-09-08
Laboratory competencesupported	From: SYN-LAB-COMPETENCE-v1 for the declared method To: SYN-LAB-COMPETENCE-v1 for the declared method	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-competence-v1` Fictional evidence reviewer · 2026-09-08
Laboratory recognition for required scopesupported	From: SYN-LAB-RECOGNITION-v1 for this receiving requirement To: SYN-LAB-RECOGNITION-v1 for this receiving requirement	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-recognition-v1` Fictional evidence reviewer · 2026-09-08
Evidence date and transition supportsupported	From: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval To: SYN-EVIDENCE-DATE-v1 / 2026-09-08 / synthetic acceptance interval	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-timing-v1` Fictional evidence reviewer · 2026-09-08
Receiving requirement acceptance basissupported	From: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only To: SYN-RECEIVING-REVIEW-v1: scoped report-use rationale only	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-acceptance-v1` Fictional evidence reviewer · 2026-09-08
Human scope and reuse reviewsupported	From: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer To: SYN-SCOPE-REVIEW-v1 by fictional evidence reviewer	Supplied as supported by the frozen synthetic fixture, solely for this receiving requirement. `SYN-R6-human-v1` Fictional evidence reviewer · 2026-09-08

Bridge limitation: SYN-BRIDGE-R6-method: SYN-METHOD-FAMILY-v1 → SYN-METHOD-FAMILY-v3; Only this directed pair and dimension within the named configurations and interval. Supports this synthetic comparison; does not rewrite the original report, establish legal acceptance, reverse direction, chain to another bridge or transfer an authorization.

Separate source-market authorization lane: No real source-market authorization supplied. A report is a separate object; target product authorization remains unresolved.

Dependency schedule · teaching work units

Every task is required. Unlimited parallel resources; no shared resource constraints, rework, holidays, queues, fees or uncertain regulatory review. This is not a quotation or launch date. A tier label adds no dependency.

Completion T: 19 teaching units

Stable dependency order: A → B → C → D → E → F → G. Critical paths (current): A → C → D → F → G.

lower of Baseline · six synthetic comparisons. Bar endpoints are exact integers. Dark bars have zero total float when completion is known; the table identifies every critical path.

Full schedule and total float
Task / required predecessors	Duration	ES	EF	LS	LF	Total float
A · Freeze scope and configuration questionsRequires none	2	0	2	0	2	0
B · Compare methods and evidenceRequires A	3	2	5	3	6	1
C · Prepare representative samplesRequires A	4	2	6	2	6	0
D · Run the planned supplementary evaluationRequires B, C	5	6	11	6	11	0
E · Resolve the local-actor/document packageRequires A	2	2	4	9	11	7
F · Complete the external review packageRequires D, E	6	11	17	11	17	0
G · Reconcile records and controlled release proposalRequires F	2	17	19	17	19	0

Specialist evidence review remains open

Even a completed schedule leaves these hard evidence holds open. A zero-duration task is not a completed source, actor or configuration decision.

All market holds · unaffected by the selected view
Hold	Question and accountable owner
H-AU-ACTOR	Who owns the local actor, language, sample and document review; which change/surveillance duties actually apply?Owner: AU compliance lead + documentation owner
H-AU-CONFIG	Which actual radio/category, national channels, power controls and antenna/installation states can this product support?Owner: AU jurisdiction specialist + RF/firmware lead
H-AU-SOURCE	Which current receiving method, lab/body recognition scope and acceptance basis cover the supplied report?Owner: AU method and evidence reviewer
H-BR-ACTOR	Who owns the local actor, language, sample and document review; which change/surveillance duties actually apply?Owner: BR compliance lead + documentation owner
H-BR-CONFIG	Which actual radio/category, national channels, power controls and antenna/installation states can this product support?Owner: BR jurisdiction specialist + RF/firmware lead
H-BR-SOURCE	Which current receiving method, lab/body recognition scope and acceptance basis cover the supplied report?Owner: BR method and evidence reviewer
H-JP-ACTOR	Who owns the local actor, language, sample and document review; which change/surveillance duties actually apply?Owner: JP compliance lead + documentation owner
H-JP-CONFIG	Which actual radio/category, national channels, power controls and antenna/installation states can this product support?Owner: JP jurisdiction specialist + RF/firmware lead
H-JP-SOURCE	Which current receiving method, lab/body recognition scope and acceptance basis cover the supplied report?Owner: JP method and evidence reviewer
H-KR-ACTOR	Who owns the local actor, language, sample and document review; which change/surveillance duties actually apply?Owner: KR compliance lead + documentation owner
H-KR-CONFIG	Which actual radio/category, national channels, power controls and antenna/installation states can this product support?Owner: KR jurisdiction specialist + RF/firmware lead
H-KR-SOURCE	Which current receiving method, lab/body recognition scope and acceptance basis cover the supplied report?Owner: KR method and evidence reviewer

Engineering consequence → record update

Carry the committed fictional rationales as exercise evidence beside the four actual source orientations. Keep hardware/firmware restrictions, specialist questions and responsible owners explicit in the expansion register.

Ungraded review

Check your understanding

Answer each question in your own words, then reveal the model answer.

01A manager says “the CE/FCC report gives us four more approvals.” What objects must you separate?
Model answer
Separate underlying measurements, the versioned report, laboratory competence/recognition, each conformity decision and each product/operating authorization. Identify a receiving requirement for each proposed report use. Existing source-market records remain independent; the four target routes need their own decisions.
02R3 has the exact method and a laboratory accreditation record. Why does it remain inspect?
Model answer
Recognition for the required receiving scope is unknown. Obtain the exact lab/body record, method/category coverage, dates and receiving acceptance basis, then record human scope review. Accreditation alone supplies competence evidence; it does not answer every recognition or acceptance question.
03What would let unequal method versions support R6, and why does that not repair R4?
Model answer
R6 has a reviewed directional bridge for its exact report, method pair, dimension, configurations, market and interval, plus receiving acceptance and human review. R4 still has independent antenna/feed and simultaneous-radio conflicts. No reverse or transitive bridge is inferred and no original report is rewritten.
04How should the RRA language discrepancy and the Certifica notice change your source record?
Model answer
Retain both RRA overview versions, the Korean notice metadata and the unread annex question; assign a Korean-source reviewer before classifying the product. Record the Anatel process date and procedure scope separately from technical rules. The notice does not resolve every pending SCH filing or demonstrate technical obsolescence.
05Calculate baseline completion and B/E float. What happens after expediting E or delaying B?
Model answer
Baseline A→C→D→F→G totals 19 units. B has one unit of total float; E has seven. E=0 leaves completion at 19 and raises E float to nine. B=5 raises completion to 20 and makes A→B→D→F→G critical. The bounded case is [16,26], with two lower-corner critical paths, not a confidence interval.
06Write a local question that could change hardware or the sequence, and propose a defensible phase.
Model answer
For example: which national category and antenna/software controls cover G02 with A1 and simultaneous radios, and what representative samples are needed? The answer may force regional firmware, a different antenna or extra evaluation before review. A defensible first phase freezes a narrower documented configuration while owners resolve the expanded scope; another phasing is valid if its constraints, holds and dependencies remain explicit.

Synthesis · a phased expansion dossier

Phase 1 — establish the actual scope. The compliance lead records target activities/dates and assigns AU/BR/JP/KR source owners. The RF/firmware lead freezes a candidate manifest and identifies antenna, region-control and concurrency assumptions. Retain teaching-node-v1, NEED-08, C-MARKET, M08-01-RAW-A, M08-01-DERIVED-A, P09-M01-C09-v1, P09-M01-C10-v1, P09-M02-U1-v1, P09-M02-U4-v1, P09-M02-U6-v1, p09-m03-europe-register-v1, P09-M04-US-v1, P09-M04-CA-v1 as parents; earlier measured, derived and pre-compliance records keep their original meaning.

Phase 2 — resolve receiving evidence. The method reviewer maps each source report to an exact receiving requirement and records every dimension, bridge and acceptance question. The sample owner proposes representatives only after configuration scope is known. Local document owners resolve actors, translations, records and marking conditions. A proposed bridge is pending review, not reusable evidence.

Phase 3 — review the release proposal. Reconcile the actual source routes, controlled configurations and open holds. The 19-unit baseline and [16,26] sensitivity describe only the fictional work package. Real durations remain unresolved; no market is declared ready from a schedule or metadata count.

RF/firmware + local specialist: which national category, antenna and software controls cover A1 and simultaneous G02 radios? The answer could change hardware, regional firmware and representative samples.
Process/document + local specialist: which actual body/lab scope and responsible actor can support this package, and what happens to a pending Brazilian submission? The answer could change review order and document dependencies.
JP/KR source owners: retrieve the current operative category/method annexes and confirm translation and transition scope before sample freeze.

Recheck on a product/firmware/antenna/concurrency change, a source or recognition update, a new intended activity/date, or the internal review-due trigger. No one has been contacted. The next lesson carries this register into lifecycle control.

Expansion register · complete static snapshot

p09-compliance-register-v1 / p09-m05-expansion-register-v1. Four source-orientation rows, separate from all SYN report comparisons. Applicability, evidence maturity, scope review and legal conclusion remain distinct. Unknown dates are explicit nulls; there is no measured compliance result or numeric legal limit in these rows.

Register handoff · four independent country questions
Record / territory	Next action / owner	State
P09-M05-AU-v1Australia	Which exact licence item, technical standard and supplier role cover N01 with A1, and what prevents an unsupported firmware region or antenna from being selected?AU jurisdiction specialist + RF/firmware lead	Applicability unresolved; source orientation only; no release decision.
P09-M05-BR-v1Brazil	Which current product act and OCD scope cover this exact configuration, and what happens to our hypothetical pending SCH filing after 2026-09-08?BR jurisdiction specialist + process/document owner	Applicability unresolved; source orientation only; no release decision.
P09-M05-JP-v1Japan	Which current Japanese category and registered-body scope cover N01/A1, and which design or software controls would make the submitted sample representative of production?JP Japanese-source reviewer + configuration owner	Applicability unresolved; source orientation only; no release decision.
P09-M05-KR-v1South Korea	Which Korean annex entry covers G02 with simultaneous transmitters and A1, and does that scope accept the proposed laboratory and single-radio source report?KR Korean-source reviewer + RF test lead	Applicability unresolved; source orientation only; no release decision.

Complete typed row · P09-M05-AU-v1

schema: p09-compliance-register-v1
snapshot: p09-m05-expansion-register-v1
id: P09-M05-AU-v1
parentIds: [ "teaching-node-v1", "NEED-08", "C-MARKET", "M08-01-RAW-A", "M08-01-DERIVED-A", "P09-M01-C09-v1", "P09-M01-C10-v1", "P09-M02-U1-v1", "P09-M02-U4-v1", "P09-M02-U6-v1", "p09-m03-europe-register-v1", "P09-M04-US-v1", "P09-M04-CA-v1" ]
module: 09.5
claim: What evidence and local decisions would support the proposed Australia expansion?
claimType: Source orientation and evidence-planning question
evaluationDate: 2026-09-09
jurisdiction: AU
territory: Australia
activity: Proposed import, placing on the market and intended radio operation; activity-specific reviews remain separate.
activityDate: Unknown / not supplied
manifest: { "id": "SYN-MAN-N01-A0-P0-F-EU-node-TX-v1", "parentId": "SYN-P09-M01-MANIFEST-v1", "scenario": "teaching-node-v1", "sku": "N01", "hardware": "SYN-HW-N01-v1", "firmware": "SYN-FW-N01-F-EU-v1", "region": "F-EU", "radios": "Node: generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35, 80 ksample/s D3; no standardized mode inferred.", "mode": "node-TX", "concurrent": false, "antenna": "A0", "antennaVersion": "SYN-A0-v1", "cable": "Internal fixed feed SYN-FEED-v1", "enclosure": "SYN-ENC-N01-v1", "supply": "P0", "supplyVersion": "SYN-P0-v1", "installation": "SYN-INSTALL-v1: indoor fixed bracket proposed; separation, mobility during service and outdoor use unresolved", "user": "SYN-USER-v1: technician installer and general end user proposed; access/service conditions unresolved", "environment": "25 °C bench identity only; operational temperature, humidity and foreseeable environment unresolved", "sample": "SYN-SAMPLE-N01-01", "regionControl": "SYN-REGION-v1: four build images exist; signed configuration, recovery and forbidden-state reachability evidence unknown", "testImageRelation": "SYN-TEST-v1 mapped to production image ID; radio-state equivalence and command limits need reviewer evidence" }
family: Spectrum / EMC / exposure / safety / telecom / documentation / continuing conformity: each requires a separate applicable basis.
applicability: { "state": "unknown", "reviewer": "AU jurisdiction specialist + RF/firmware lead", "rationale": "N01 generic telemetry transmitter is the candidate. Its actual equipment and compliance level are unresolved. Wi-Fi G02 and cellular G03 need separate category/function reviews." }
authority: { "ids": [ "AU1", "AU2", "AU3", "AU4", "AU5", "AU6", "AU7", "AU8" ], "version": "Per-source versions in the 2026-09-09 ledger; no combined legal version", "role": "ACMA; Radiocommunications Act framework, General Equipment Rules 2021 and relevant national operating licence. Guidance identifies the source chain; selected operative provisions are not yet resolved.", "locator": "Linked official source cards; selected product clause remains open", "language": "English", "status": "Orientation reviewed; incomplete product route" }
measurement: { "method": "Determine the actual Schedule 5 / product technical standards, editions, compliance level and any recognition arrangement. AU3 describes conditional evidence routes, not blanket foreign-report acceptance.", "quantity": "No compliance measurement supplied", "unit": null, "value": null, "statistic": "Unspecified — no numeric result", "detector": "Unspecified", "bandwidth": "Unspecified regulatory measurement bandwidth", "distance": "Unspecified", "plane": "Unspecified", "uncertainty": "Not evaluated; no pass/fail calculation" }
actor: Name the responsible supplier and any agency arrangement. Supplier registration and electrical safety scheme roles require their own applicability checks.
responsibility: Identify declaration and technical records, English documentation needs, retention conditions, model identification and eligible RCM/e-label presentation. Artwork follows the rule and actor review.
evidence: { "id": "P09-M05-AU-SOURCE-ORIENTATION-v1", "configuration": "SYN-MAN-N01-A0-P0-F-EU-node-TX-v1", "version": "v1", "maturity": "Source orientation, not measured compliance evidence", "scope": "N01 candidate with explicit gateway/antenna expansion questions", "scopeMatch": "Unknown: no product-specific formal evidence mapped", "review": "Educational source review; specialist product review open", "legalConclusion": "No authorization, acceptance or release conclusion" }
dates: { "publication": null, "entryIntoForce": null, "application": null, "transitionEnd": null, "access": "2026-09-09", "reviewed": "2026-09-09", "reviewDue": "2026-12-08" }
unresolved: [ "Review a specific LIPD Class Licence 2025 item and all associated conditions. No national power, bandwidth, antenna, duty-cycle or use permission is assigned from 2.450 GHz alone.", "Determine the actual Schedule 5 / product technical standards, editions, compliance level and any recognition arrangement. AU3 describes conditional evidence routes, not blanket foreign-report acceptance.", "Define representative N01 and changed-antenna/gateway configurations. Laboratory competence and, where required, accreditation/recognition must cover the selected method. No mandatory local test or sample count is assumed.", "Review material antenna, firmware, enclosure and supply changes against the evidence. Factory audit, surveillance or renewal is not asserted universally; each duty needs a cited applicable basis or reviewed non-applicability.", "A national operating condition could invalidate the unreviewed global firmware hypothesis or require antenna/power restrictions." ]
nextAction: Which exact licence item, technical standard and supplier role cover N01 with A1, and what prevents an unsupported firmware region or antenna from being selected?
owner: AU jurisdiction specialist + RF/firmware lead
dependencies: [ "Controlled configuration and intended activity/date", "Current category and national conditions", "Method/body/lab acceptance", "Representative samples", "Responsible actors and language/label package" ]

Complete typed row · P09-M05-BR-v1

schema: p09-compliance-register-v1
snapshot: p09-m05-expansion-register-v1
id: P09-M05-BR-v1
parentIds: [ "teaching-node-v1", "NEED-08", "C-MARKET", "M08-01-RAW-A", "M08-01-DERIVED-A", "P09-M01-C09-v1", "P09-M01-C10-v1", "P09-M02-U1-v1", "P09-M02-U4-v1", "P09-M02-U6-v1", "p09-m03-europe-register-v1", "P09-M04-US-v1", "P09-M04-CA-v1" ]
module: 09.5
claim: What evidence and local decisions would support the proposed Brazil expansion?
claimType: Source orientation and evidence-planning question
evaluationDate: 2026-09-09
jurisdiction: BR
territory: Brazil
activity: Proposed import, placing on the market and intended radio operation; activity-specific reviews remain separate.
activityDate: Unknown / not supplied
manifest: { "id": "SYN-MAN-N01-A0-P0-F-EU-node-TX-v1", "parentId": "SYN-P09-M01-MANIFEST-v1", "scenario": "teaching-node-v1", "sku": "N01", "hardware": "SYN-HW-N01-v1", "firmware": "SYN-FW-N01-F-EU-v1", "region": "F-EU", "radios": "Node: generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35, 80 ksample/s D3; no standardized mode inferred.", "mode": "node-TX", "concurrent": false, "antenna": "A0", "antennaVersion": "SYN-A0-v1", "cable": "Internal fixed feed SYN-FEED-v1", "enclosure": "SYN-ENC-N01-v1", "supply": "P0", "supplyVersion": "SYN-P0-v1", "installation": "SYN-INSTALL-v1: indoor fixed bracket proposed; separation, mobility during service and outdoor use unresolved", "user": "SYN-USER-v1: technician installer and general end user proposed; access/service conditions unresolved", "environment": "25 °C bench identity only; operational temperature, humidity and foreseeable environment unresolved", "sample": "SYN-SAMPLE-N01-01", "regionControl": "SYN-REGION-v1: four build images exist; signed configuration, recovery and forbidden-state reachability evidence unknown", "testImageRelation": "SYN-TEST-v1 mapped to production image ID; radio-state equivalence and command limits need reviewer evidence" }
family: Spectrum / EMC / exposure / safety / telecom / documentation / continuing conformity: each requires a separate applicable basis.
applicability: { "state": "unknown", "reviewer": "BR jurisdiction specialist + process/document owner", "rationale": "Assess whether N01 belongs to the restricted-radiation equipment scope of Act 14448/2017 as amended. G02/G03 radio functions and concurrency are separate facts; the generic waveform is not a named technology category." }
authority: { "ids": [ "BR1", "BR2", "BR3" ], "version": "Per-source versions in the 2026-09-09 ledger; no combined legal version", "role": "Anatel; Resolution 715/2019 as amended. Product-specific technical acts and the actual equipment category remain necessary.", "locator": "Linked official source cards; selected product clause remains open", "language": "Portuguese; lesson paraphrase", "status": "Orientation reviewed; incomplete product route" }
measurement: { "method": "Map current technical act clauses, method versions, report acceptance and lab/body scope. R2’s fictional method conflict says nothing about an actual Brazilian test report.", "quantity": "No compliance measurement supplied", "unit": null, "value": null, "statistic": "Unspecified — no numeric result", "detector": "Unspecified", "bandwidth": "Unspecified regulatory measurement bandwidth", "distance": "Unspecified", "plane": "Unspecified", "uncertainty": "Not evaluated; no pass/fail calculation" }
actor: Name the applicant/responsible local role and the selected OCD only after checking category and scope. A portal account is not a technical certification decision.
responsibility: Confirm Portuguese documentation, declarations, reports, model identity and identification/label format. The 2026-09-08 notice changes the described submission path; pending SCH filings require an explicit status check.
evidence: { "id": "P09-M05-BR-SOURCE-ORIENTATION-v1", "configuration": "SYN-MAN-N01-A0-P0-F-EU-node-TX-v1", "version": "v1", "maturity": "Source orientation, not measured compliance evidence", "scope": "N01 candidate with explicit gateway/antenna expansion questions", "scopeMatch": "Unknown: no product-specific formal evidence mapped", "review": "Educational source review; specialist product review open", "legalConclusion": "No authorization, acceptance or release conclusion" }
dates: { "publication": null, "entryIntoForce": null, "application": null, "transitionEnd": null, "access": "2026-09-09", "reviewed": "2026-09-09", "reviewDue": "2026-12-08" }
unresolved: [ "Select current national technical clauses for the actual transmitter. No allowed channel, output power, antenna condition or operating entitlement has been inferred from the candidate act.", "Map current technical act clauses, method versions, report acceptance and lab/body scope. R2’s fictional method conflict says nothing about an actual Brazilian test report.", "Ask the scoped OCD/evidence reviewer which variants, antenna modes, samples, lab route and manufacturing information this category needs. Local testing and sample quantities remain unassigned.", "Resolution 715 distinguishes certification models, periodic evaluation and change review. Determine applicable maintenance, manufacturing-quality evaluation and identification duties; do not invent a universal renewal interval.", "A changed A1 antenna or G02 simultaneous state may expand samples and evaluation. A pending filing’s administrative path could change document dependencies without changing RF evidence." ]
nextAction: Which current product act and OCD scope cover this exact configuration, and what happens to our hypothetical pending SCH filing after 2026-09-08?
owner: BR jurisdiction specialist + process/document owner
dependencies: [ "Controlled configuration and intended activity/date", "Current category and national conditions", "Method/body/lab acceptance", "Representative samples", "Responsible actors and language/label package" ]

Complete typed row · P09-M05-JP-v1

schema: p09-compliance-register-v1
snapshot: p09-m05-expansion-register-v1
id: P09-M05-JP-v1
parentIds: [ "teaching-node-v1", "NEED-08", "C-MARKET", "M08-01-RAW-A", "M08-01-DERIVED-A", "P09-M01-C09-v1", "P09-M01-C10-v1", "P09-M02-U1-v1", "P09-M02-U4-v1", "P09-M02-U6-v1", "p09-m03-europe-register-v1", "P09-M04-US-v1", "P09-M04-CA-v1" ]
module: 09.5
claim: What evidence and local decisions would support the proposed Japan expansion?
claimType: Source orientation and evidence-planning question
evaluationDate: 2026-09-09
jurisdiction: JP
territory: Japan
activity: Proposed import, placing on the market and intended radio operation; activity-specific reviews remain separate.
activityDate: Unknown / not supplied
manifest: { "id": "SYN-MAN-N01-A0-P0-F-EU-node-TX-v1", "parentId": "SYN-P09-M01-MANIFEST-v1", "scenario": "teaching-node-v1", "sku": "N01", "hardware": "SYN-HW-N01-v1", "firmware": "SYN-FW-N01-F-EU-v1", "region": "F-EU", "radios": "Node: generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35, 80 ksample/s D3; no standardized mode inferred.", "mode": "node-TX", "concurrent": false, "antenna": "A0", "antennaVersion": "SYN-A0-v1", "cable": "Internal fixed feed SYN-FEED-v1", "enclosure": "SYN-ENC-N01-v1", "supply": "P0", "supplyVersion": "SYN-P0-v1", "installation": "SYN-INSTALL-v1: indoor fixed bracket proposed; separation, mobility during service and outdoor use unresolved", "user": "SYN-USER-v1: technician installer and general end user proposed; access/service conditions unresolved", "environment": "25 °C bench identity only; operational temperature, humidity and foreseeable environment unresolved", "sample": "SYN-SAMPLE-N01-01", "regionControl": "SYN-REGION-v1: four build images exist; signed configuration, recovery and forbidden-state reachability evidence unknown", "testImageRelation": "SYN-TEST-v1 mapped to production image ID; radio-state equivalence and command limits need reviewer evidence" }
family: Spectrum / EMC / exposure / safety / telecom / documentation / continuing conformity: each requires a separate applicable basis.
applicability: { "state": "unknown", "reviewer": "JP Japanese-source reviewer + configuration owner", "rationale": "Identify the actual specified radio-equipment category from current Japanese text. Neither the 2013 English translation nor a TELEC service description chooses N01’s category." }
authority: { "ids": [ "JP1", "JP2", "JP3", "JP4" ], "version": "Per-source versions in the 2026-09-09 ledger; no combined legal version", "role": "MIC / Radio Act and the specified radio-equipment certification ordinance. Current e-Gov version metadata was retrieved; operative category and transition clauses still need review.", "locator": "Linked official source cards; selected product clause remains open", "language": "Japanese current source gap; historical English and body guidance", "status": "Orientation reviewed; incomplete product route" }
measurement: { "method": "Resolve current MIC method notices and editions, lab/report acceptance, body recognition and any scoped alternative method bridge. R3 intentionally leaves recognition unknown.", "quantity": "No compliance measurement supplied", "unit": null, "value": null, "statistic": "Unspecified — no numeric result", "detector": "Unspecified", "bandwidth": "Unspecified regulatory measurement bandwidth", "distance": "Unspecified", "plane": "Unspecified", "uncertainty": "Not evaluated; no pass/fail calculation" }
actor: Assign the manufacturer/applicant, authorized contact and registered-body review roles for the chosen route. The lesson has not verified a current body listing for this exact equipment category.
responsibility: Confirm Japanese application/technical material, labels or permitted electronic identification, design consistency and required records from the actual route. Do not treat the historical English translation as current instructions.
evidence: { "id": "P09-M05-JP-SOURCE-ORIENTATION-v1", "configuration": "SYN-MAN-N01-A0-P0-F-EU-node-TX-v1", "version": "v1", "maturity": "Source orientation, not measured compliance evidence", "scope": "N01 candidate with explicit gateway/antenna expansion questions", "scopeMatch": "Unknown: no product-specific formal evidence mapped", "review": "Educational source review; specialist product review open", "legalConclusion": "No authorization, acceptance or release conclusion" }
dates: { "publication": null, "entryIntoForce": null, "application": null, "transitionEnd": null, "access": "2026-09-09", "reviewed": "2026-09-09", "reviewDue": "2026-12-08" }
unresolved: [ "Review national frequency, emission, antenna, power and use conditions for the identified category. Station licensing or other operating obligations remain separate questions where relevant.", "Resolve current MIC method notices and editions, lab/report acceptance, body recognition and any scoped alternative method bridge. R3 intentionally leaves recognition unknown.", "TELEC describes application specifications, diagrams, photographs, specimen/data paths and construction-conformance verification material. Confirm the actual product route and body requirements before selecting samples.", "Ask what construction-design controls, changes, continuing conformity, records and any required follow-up apply. No universal factory audit or certificate expiry is assigned.", "A category-specific antenna or software-control requirement could force a regional image or hardware variant before samples can be frozen." ]
nextAction: Which current Japanese category and registered-body scope cover N01/A1, and which design or software controls would make the submitted sample representative of production?
owner: JP Japanese-source reviewer + configuration owner
dependencies: [ "Controlled configuration and intended activity/date", "Current category and national conditions", "Method/body/lab acceptance", "Representative samples", "Responsible actors and language/label package" ]

Complete typed row · P09-M05-KR-v1

schema: p09-compliance-register-v1
snapshot: p09-m05-expansion-register-v1
id: P09-M05-KR-v1
parentIds: [ "teaching-node-v1", "NEED-08", "C-MARKET", "M08-01-RAW-A", "M08-01-DERIVED-A", "P09-M01-C09-v1", "P09-M01-C10-v1", "P09-M02-U1-v1", "P09-M02-U4-v1", "P09-M02-U6-v1", "p09-m03-europe-register-v1", "P09-M04-US-v1", "P09-M04-CA-v1" ]
module: 09.5
claim: What evidence and local decisions would support the proposed South Korea expansion?
claimType: Source orientation and evidence-planning question
evaluationDate: 2026-09-09
jurisdiction: KR
territory: South Korea
activity: Proposed import, placing on the market and intended radio operation; activity-specific reviews remain separate.
activityDate: Unknown / not supplied
manifest: { "id": "SYN-MAN-N01-A0-P0-F-EU-node-TX-v1", "parentId": "SYN-P09-M01-MANIFEST-v1", "scenario": "teaching-node-v1", "sku": "N01", "hardware": "SYN-HW-N01-v1", "firmware": "SYN-FW-N01-F-EU-v1", "region": "F-EU", "radios": "Node: generic 2.450 GHz QPSK; 20 kbit/s information, 10 ksymbol/s, RRC α=0.35, 80 ksample/s D3; no standardized mode inferred.", "mode": "node-TX", "concurrent": false, "antenna": "A0", "antennaVersion": "SYN-A0-v1", "cable": "Internal fixed feed SYN-FEED-v1", "enclosure": "SYN-ENC-N01-v1", "supply": "P0", "supplyVersion": "SYN-P0-v1", "installation": "SYN-INSTALL-v1: indoor fixed bracket proposed; separation, mobility during service and outdoor use unresolved", "user": "SYN-USER-v1: technician installer and general end user proposed; access/service conditions unresolved", "environment": "25 °C bench identity only; operational temperature, humidity and foreseeable environment unresolved", "sample": "SYN-SAMPLE-N01-01", "regionControl": "SYN-REGION-v1: four build images exist; signed configuration, recovery and forbidden-state reachability evidence unknown", "testImageRelation": "SYN-TEST-v1 mapped to production image ID; radio-state equivalence and command limits need reviewer evidence" }
family: Spectrum / EMC / exposure / safety / telecom / documentation / continuing conformity: each requires a separate applicable basis.
applicability: { "state": "unknown", "reviewer": "KR Korean-source reviewer + RF test lead", "rationale": "The Korean overview lists certification, registration, self-confirmation and interim certification; the English overview lists three. Resolve the applicable annex for N01 and each gateway radio function from Korean sources." }
authority: { "ids": [ "KR1", "KR2", "KR3", "KR4", "KR5" ], "version": "Per-source versions in the 2026-09-09 ledger; no combined legal version", "role": "RRA; Radio Waves Act Article 58-2 orientation and conformity-assessment notice 2026-4. Current Korean annex/transition text is not yet read.", "locator": "Linked official source cards; selected product clause remains open", "language": "Korean and English discrepancy; annex unread", "status": "Orientation reviewed; incomplete product route" }
measurement: { "method": "Read notice 2026-4 and lab designation notice 2026-5, then verify method/edition, test body scope, any MRA parties/phase/dates and report acceptance. The attachments remain a named source gap.", "quantity": "No compliance measurement supplied", "unit": null, "value": null, "statistic": "Unspecified — no numeric result", "detector": "Unspecified", "bandwidth": "Unspecified regulatory measurement bandwidth", "distance": "Unspecified", "plane": "Unspecified", "uncertainty": "Not evaluated; no pass/fail calculation" }
actor: Identify the applicant, local representative or responsible party where required by the selected procedure. Assign Korean-source translation and evidence review owners before finalizing the package.
responsibility: Confirm Korean documentation, product/model identity, conformity record and marking/e-label conditions from the operative procedure; no generic worldwide label template is assumed.
evidence: { "id": "P09-M05-KR-SOURCE-ORIENTATION-v1", "configuration": "SYN-MAN-N01-A0-P0-F-EU-node-TX-v1", "version": "v1", "maturity": "Source orientation, not measured compliance evidence", "scope": "N01 candidate with explicit gateway/antenna expansion questions", "scopeMatch": "Unknown: no product-specific formal evidence mapped", "review": "Educational source review; specialist product review open", "legalConclusion": "No authorization, acceptance or release conclusion" }
dates: { "publication": null, "entryIntoForce": null, "application": null, "transitionEnd": null, "access": "2026-09-09", "reviewed": "2026-09-09", "reviewDue": "2026-12-08" }
unresolved: [ "Identify the actual national technical criteria, permitted modes, channels, antenna/power conditions and installation restrictions. A shared carrier or a Wi-Fi name cannot answer these questions.", "Read notice 2026-4 and lab designation notice 2026-5, then verify method/edition, test body scope, any MRA parties/phase/dates and report acceptance. The attachments remain a named source gap.", "Resolve representative samples and designated/recognized laboratory requirements for the actual category. A foreign accreditation badge alone cannot close the recognition question.", "Identify applicable change notification, continuing conformity, sample follow-up, factory or renewal provisions in the actual category. Unread text is unknown, not not-applicable.", "G02’s concurrent radios and changed A1/feed may require a different representative configuration and additional evidence before external review can start." ]
nextAction: Which Korean annex entry covers G02 with simultaneous transmitters and A1, and does that scope accept the proposed laboratory and single-radio source report?
owner: KR Korean-source reviewer + RF test lead
dependencies: [ "Controlled configuration and intended activity/date", "Current category and national conditions", "Method/body/lab acceptance", "Representative samples", "Responsible actors and language/label package" ]

References and source recheck record

Actual access and educational source review: 2026-09-09. Read scope is stated for each source. Publication or displayed revision dates are not automatically entry-into-force or application dates; unverified operative dates remain open. Internal recheck due through 2026-12-08, earlier on a relevant change. The fictional planner retains its separate 2026-09-08 / 2026-12-07 inputs.

ITU · ITU · Radio Regulations, 2024 edition
International allocation context · 2024 edition catalogue. Catalogue read; no national permission inferred. The catalogue identifies the edition incorporating WRC-23. A national product and operating route still needs its own sources.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
AU1 · ACMA · Five steps for suppliers
Regulator workflow guidance · Live guidance accessed 2026-09-09. Read. Check rules, assemble evidence, sign and keep records, check supplier registration and label requirements. The applicable product rules determine each obligation.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
AU2 · ACMA · Check the rules
Product-family and rule orientation · General Equipment Rules 2021 / LIPD Class Licence 2025 references. Read; selected product provisions remain open. Radio, EMC, electromagnetic energy and telecommunications questions are distinct. Identify the relevant schedules and the actual product before selecting tests.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
AU3 · ACMA · Show your product complies
Evidence and laboratory guidance · Updated 2026-09-04. Read. Evidence depends on the applicable compliance level and family. Accreditation is required in specified cases. The guidance describes Australia as participating in APEC TEL Phase I, not Phase II; a particular report still needs a scoped acceptance review.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
AU4 · ACMA · Sign and keep records
Documentation guidance · Updated 2025-03-31. Read. Identify the product and supporting evidence, the responsible signatory, record language and applicable retention conditions. Agency arrangements do not erase the need to assign responsibility.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
AU5 · ACMA · Register the responsible supplier
Supplier registration guidance · Live guidance accessed 2026-09-09. Read. Check whether the ACMA labelling rules require registration for the product; do not assume every device has an identical registration obligation.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
AU6 · ACMA · Label your product
Marking guidance · Updated 2025-03-31. Read. RCM and any eligible alternative or electronic presentation depend on the applicable rules. Electrical safety scheme responsibilities need a separate check.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
AU7 · ACMA · LIPD class licence
National operating-conditions orientation · Updated 2025-10-02; 2025 licence. Guidance read; no selected licence item. Shared spectrum use remains subject to licence conditions. The carrier alone does not select the permitted device class, power, antenna or use conditions.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
AU8 · ACMA · Know what you must do
Supplier and product-change guidance · Live guidance accessed 2026-09-09. Read. Assess product changes and maintain supporting records. Overseas marking alone does not establish compliance with ACMA requirements.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
BR1 · Anatel · Resolution 715/2019
Consolidated certification and homologation regulation · Web consolidation includes Resolution 780/2025 amendments. Relevant articles read in Portuguese. Articles 36–50 distinguish certification models, OCD involvement, maintenance and changes. Articles 55–63 address homologation, documentation and identification. Product-specific acts still determine the actual technical route.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
BR2 · Anatel · Certifica transition notice
Administrative process notice · Published 2026-09-03; modified 2026-09-08. Read in Portuguese. From 2026-09-08, Certifica receives the described procedures and SCH stops new requests. Specified own-use processes temporarily remain in SEI. The notice says certification and homologation rules do not change. It does not settle every pending SCH filing.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
BR3 · Anatel · Act 14448/2017, restricted-radiation requirements
Technical requirement candidate · Amended web text; title is 14448 despite URL ending 14451. Scope and amendment references read; no selected product clause. Annex I covers restricted-radiation equipment. Whether this product belongs there, which current clauses apply and what samples/methods they require remain specialist questions.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
JP1 · e-Gov · Specified radio-equipment certification ordinance
Current Japanese legal source · Current-version metadata: 2026-07-30; MIC ordinance 95/2026. Version/history and contents headings read; operative clauses not retrieved. The exact current equipment category, applicable provisions and transition text require Japanese legal-source review. Metadata is not a verified category decision.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
JP2 · Ministry of Justice · English ordinance translation
Historical English orientation · Translation reflects amendment 122/2013. Read; not current law. The translation distinguishes technical regulation conformity certification and construction-type routes. Its old version cannot establish the current Japanese category or acceptance conditions.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
JP3 · TELEC · Technical regulation conformity certification
Representative certification-body service description · Live service page accessed 2026-09-09. Read; representative procedure only. Describes test certification and construction-design certification, application material, specimens or submitted data and verification documentation. Confirm the chosen body’s current registration and equipment scope separately.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
JP4 · MIC · Radio equipment technical certification site
Regulator source requiring renewed retrieval · Access attempt 2026-09-09. Official error page returned; substantive content not read. Resolve the current MIC destination, registered-body scope, category and method references before drawing a route conclusion.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
KR1 · RRA · Korean conformity-assessment overview
Regulator category orientation · Live Korean overview accessed 2026-09-09. Read; English paraphrase here is not a certified translation. Lists four categories under Radio Waves Act Article 58-2: certification, registration, self-confirmation and interim certification. The applicable product annex must still be read.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
KR2 · RRA · English conformity-assessment overview
English regulator overview · Live English page accessed 2026-09-09. Read; category count differs from Korean page. Lists three categories. This language discrepancy is an explicit source-review gap, not a reason to choose the easier route.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
KR3 · RRA · Conformity-assessment notice record
Current notice and revision metadata · Notice 2026-4, 2026-07-24. Record and revision dates read; attachment not read. Obtain the Korean annex and operative transition provisions. The listing date does not by itself prove an application date or a product category.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
KR4 · RRA · Laboratory designation and management notice record
Laboratory recognition source metadata · Notice 2026-5, 2026-08-21. Record and revision dates read; attachment not read. Check the exact laboratory, method, recognition scope and applicable dates from the operative text and current records.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
KR5 · RRA · Mutual recognition arrangements
MRA mechanism guidance · Live guidance accessed 2026-09-09. Read; no bilateral arrangement selected. Phase I concerns testing and laboratories; Phase II concerns certification bodies and certificates. Receiving technical requirements remain relevant. Parties, phase, dates and equipment scope must be verified for a proposed use.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
US · eCFR · 47 CFR Part 2, Subpart J
U.S. equipment-authorization rules · Displayed current through 2026-09-04. Sections 2.901, 2.906, 2.907 and 2.948 read. Certification and supplier declaration are distinct procedures. Section 2.948 distinguishes laboratory accreditation and Commission recognition for certification testing. This is a source-market example, not target-market acceptance.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
EU · EUR-Lex · Radio Equipment Directive
Original EU directive · 2014 original act; not a current harmonised-standards list. Articles 10, 16 and 17 read. Technical documentation, conformity assessment and marking have defined roles. Current amendments, citations and product requirements remain in the separate 09.3 route review.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.
CA · ISED · REC-LAB recognition procedure
Canadian laboratory recognition source · 09.4 retains its earlier source record. Live access 2026-09-09 blocked; not reverified. Carry the Canadian evidence question forward; retrieve and review the current procedure before using it for a new receiving requirement.
Access/review 2026-09-09; owner: relevant jurisdiction/source reviewer. Recheck the current product-specific operative text and activity date before use.