Development and publication work have resumed. Service APIs remain unavailable unless explicitly documented as live.
Institutional Record
Meaningful changes, dated without operational detail.
This record covers changes to the public mandate, policy, site structure, and material service status. Deployment identifiers, authentication architecture, recovery controls, host topology, migrations, and private operations remain in protected records.
Entries
Messages and Dropkit are recorded without a launch claim
New public status pages describe the planned Triluna Messages and Triluna Dropkit service boundaries. Messages remains disabled until a reviewed end-to-end encrypted delivery design exists. Dropkit remains free by policy but has exactly 0 KB of production transfer capacity and a maximum retention policy of 24 hours. Neither page offers a message composer, upload control, storage allocation, or account flow.
Messages
Secure communications model; delivery not available
Dropkit
Free transfer model; 0 KB capacity; at most 24 hours retention
Public state
Status record only; no service activation is claimed
Public record boundary narrowed
The Institutional Record now describes public policy, meaningful publication changes, and user-visible service status. Internal identifiers, authentication and recovery design, deployment evidence, migration notes, capability names, and control-plane details are no longer treated as public release notes.
Public scope
Mandate, policy, site structure, and material service status
Protected scope
Credentials, recovery controls, host topology, migrations, and operations
Change
Public wording and publication boundary
Renkan ID remains the shared identity boundary
Renkan ID is the persistent identity authority for participating projects. A project may keep its own data, permissions, and service responsibilities; the public record does not create a parallel account system or imply that recognition grants authority.
Identity
Renkan ID only
Project ownership
Data and authorisation remain with each project
Public state
Reference boundary; no new account claim
Relay status is separated from catalogue language
Triluna Relay remains launch-gated in the public record. Reference descriptions of Open Access or paid plans do not by themselves mean that registration, provisioning, billing, API use, or customer support is available. The current capability matrix is published by the Relay surface and must be read together with its live evidence.
Catalogue
Reference text only until service activation is evidenced
Customer state
New registration and provisioning are not claimed as available
Billing
No public billing activation is claimed here
Open Ledger remains explicitly under review
The public accounting view continues to distinguish recorded expenditure, pending support details, and categories that have not been reported. It is a publication of the supplied record, not a closed account or an audit. Accounting is stated as of August 21, 2026; the reconciliation date is not published.
Accounting as of
August 21, 2026
Reconciliation date
Not published
Boundary
Unknown, pending, and received values remain distinct
Legal and contribution boundaries remain explicit
Fundatio Trilunae remains an independent public-interest initiative in formation. It is not a legally constituted foundation, legal person, charity, nonprofit organisation, or grant-making body. Public donations and payment collection are not presented as active services.
Legal status
Initiative in formation; not a constituted foundation
Public contributions
Not solicited or accepted through triluna.org
Correction policy
Material changes are recorded explicitly
Triluna Document Standard 1.0 published across the document family
The public TDS page records Version 1.0 as the shared document contract for Triluna, RENKAN, and Gekka Harae. Its public scope covers page geometry, typography, metadata, versioning, templates, and release boundaries. Working templates and examples are labelled as working material rather than official release documents.