Uniform Resource Locator

Outcome: Design or review URL for this system while keeping data correct, secure, and easy to operate. User context: An invoice link uses a stable path and query. A fragment jumps to the disputed line item. Technical concept or control: URL. Why it fits: Make URLs stable and shareable. Use clear encoding, one main URL, and proper access checks. Do not use it when: Never place secrets in URLs or use fragments for server data. Add redirects before changing public paths. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.