Start at the front door and choose a scope

Why this matters

The front door helps a human find a context. It does not decide which company owns an identity, and it does not grant an agent access to the records behind a result.

A client needs to know whether they are exploring the fixed anonymous sample or entering a protected source library before making any design decisions.

Step by step

1. 01

   Orient yourself in the introduction

   Screen or control: Home, Products and the five pillar links

   Why: The menu expresses the solution stack, while the introductory page supplies the purpose. Neither proves an implemented physical connection.

   How: Read the five pillar labels and follow the learning link before selecting a protected library. Keep the current easy introduction available as your orientation.

   What you should see: You can explain what each pillar contributes to one composition.

   Verify: Name one record needed at each pillar without naming a company or inventing a key.

2. 02

   Compare discovery with exact resolution

   Screen or control: Prefix & identity and Resolve context

   Why: A display label can lead to several distinct source records. Selecting a label cannot establish equivalence between them.

   How: Use the anonymous P1 resolver for the supplied GIAI. Compare its source occurrences with the same object in P5 rather than treating the result count as a count of machines.

   What you should see: The sample retains its demonstration prefix and exact existing identity.

   Verify: Check the source pointer on every result and retain the non-issued state.

3. 03

   Read the access boundary

   Screen or control: Account and the private workspace gate

   Why: The platform must protect client context while allowing public education to remain useful.

   How: If a protected page refuses access, record that limitation and continue in the anonymous sample. Do not change roles or substitute another customer record to finish an exercise.

   What you should see: Public education remains available; private records remain scoped.

   Verify: A refusal is not evidence that the company has no data, and a successful login is not company authority.

What is happening under the surface

A search term is a discovery input, not a new identifier. Preserve the original prefix, key and source assertion returned by the selected record.

The account principal, the selected record and the authority to amend that record are separate facts. A signed-in account is not automatically a company-authorized decision maker.

Common mistakes

• Counting matched occurrences as separate physical units.
• Using navigation or account ownership as evidence of customer authority.

The records an agent needs

Discovery is a human navigation step. An agent still needs the exact retained identity, source occurrence and authorization scope; none is inferred from the search label.

Pointers locate records; hashes pin bytes; lesson numbers locate teaching material. None substitutes for an applicable assigned GS1 identity.

Apply what you learned

Draw a short route from introduction to exact sample identity to source evidence.

Prepare these outputs

• A five-pillar role description.
• The exact sample GIAI and at least one source pointer.
• A sentence distinguishing discovery from permission.

Review your work against these checks

• The prefix and identifier are unchanged.
• Private access remains unchanged.
• No company, installation or execution claim is inferred.

Source and current boundaries

Authored teaching about the current navigation and protected source boundary. The anonymous resolver searches only its fixed educational model.

Reading, answering a question and opening a diagram do not issue identifiers, validate a scientific method, establish company authority, commission an environment or authorize physical action.