Development status

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

Dropkit's public status records its production limits

The status page now identifies Dropkit as capacity-unavailable, states that production transfer capacity is exactly 0 KB, and sets a 24-hour retention ceiling for any future transfer. The existing service contract is unchanged and Dropkit remains unavailable.

Patronatus remains dormant

Public wording now states that Ronova operates and publishes Triluna, distinguishes its legal status from the canonical motto, and describes current publication and service availability. The proof-checker page identifies its testnet scope. TDS 1.0 is limited to page-based publications. Ledger wording follows the current supplied snapshot; the source record itself was not changed.

The former TDS routes now lead to the dedicated site

The English, German, French, Japanese, and Traditional Chinese TDS addresses on triluna.org now redirect permanently to the matching edition at tds.triluna.org. Each language edition is the canonical page for its route.

Triluna Document Standard 1.0 has a dedicated public home

The public TDS 1.0 reference now has a five-language home at tds.triluna.org. It provides a Markdown template and a text-only HTML sample; both are working examples, not official release documents. Ronova Syuku remains in development. The existing four-style WOFF2 package is published with its OFL notice; no TTF files are included, and glyph coverage remains under review.

Document Rescue and Dropbox exporter developer previews are published

Five-language pages at rescue.triluna.org provide unsigned Chrome Standard and Chrome Advanced packages for manual testing. A separate source package at dropbox.triluna.org contains the optional client-side Dropbox export provider; it is not a hosted transfer service. The Dropbox-enabled extension remains undistributed until its public app key and stable redirect identity are configured. Neither page claims a Chrome Web Store release or live Dropbox authorization.

Ronova Syuku now has four native styles

The self-hosted font now includes Regular, Bold, Italic and BoldItalic, with individually approved designs for 戶、你、查. Other glyphs remain subject to review.

Regular: 戶你查 · Bold: 戶你查 · Italic: 戶你查 · BoldItalic: 戶你查

Relay is stated as a Triluna subdomain; the donation sandbox is public

Relay is now labelled as the service at relay.triluna.org, rather than a peer institutional site. The homepage has a visible Donate button. Its public sandbox selects a transient regional display currency, keeps every amount at zero, and can create only a browser-local printable ceremonial certificate; it creates no form submission, payment, account, receipt, certificate artifact, or record.

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.

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.

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.

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.

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.

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.

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.