Mission
Language is part of trust.
An agent cannot be accountable if its intent changes in translation, its evidence is unreadable to the principal, or its interface excludes the script a community uses. Internationalization therefore belongs in Web7’s identity, intent, policy, evidence, and interface layers—not as a final localization pass.
Core invariant
The meaning, authority, and auditability of an AMP intent must survive
locale changes without silently changing the signed payload.
Activity map
Learn, build, review.
A working surface for language enablement, implementation support, and community education across the Web7 stack.
01 / enable
Language enablement
02 / build
Developer support
03 / share
Education & outreach
Grounded answers
Ask the i18n corpus.
Search curated W3C internationalization guidance with multilingual retrieval. Answers are constrained to indexed source passages and link back to the material used.
Answers cite the indexed sources. Your question is recorded only as a one-way hash.
Locale laboratory
Same data. Local expectations.
Locale-aware output is a runtime behavior, not translated decoration. Compare standards-based formatting without changing the underlying values.
Amount
₹12,34,567.89
Date
Friday, 24 July 2026
Participants
Principal, agent, and auditor
The locale changes presentation only. Signed AMP values remain canonical, deterministic, and independently verifiable.
Design principles
Internationalization by construction.
Meaning before strings
Store structured intent and evidence. Localize its human representation without mutating the signed semantic payload.
Direction is structural
Components support left-to-right, right-to-left, and mixed-direction content without mirrored meaning or broken controls.
Unicode end to end
Identity, search, policy, logs, and evidence preserve normalized Unicode while retaining the original user expression.
Localize the audit trail
Principals and reviewers can inspect the same accountable event graph in their locale and verify it against one canonical record.
Architecture
Where i18n lives in Web7.
Internationalization crosses the stack. Each layer has a distinct, testable responsibility.
L2
kynetraauth + KTL
Internationalized names, identifiers, credentials, consent, and policy presentation.
L4
Kynetra Prime
Locale-aware understanding with explicit confidence, source language, and translation provenance.
L5
ClearScript
Typed messages, locale metadata, plural rules, and compile-time detection of unsafe string construction.
L6
HBForge
Accessible global components, bidirectional layout primitives, locale negotiation, and formatters.
L7
Applications
Validated translations, local workflows, culturally appropriate content, and community review.
Activity
Working updates.
Internationalization Activity charter
Initial mission, resource map, design principles, and cross-stack responsibilities prepared for community review.
Locale metadata for AMP envelopes
Define BCP 47 language metadata, canonical payload rules, and translation provenance without changing signature semantics.
HBForge global component conformance
Test bidirectional layout, text expansion, font fallback, input methods, and locale-sensitive formatting.
Participate
Bring your language to Web7.
We need language experts, implementers, translators, accessibility reviewers, and people who know where software fails their community.