Skip to content

Weekly This Week in Matrix update

1. Purpose and boundary

This Week in Matrix (TWiM) is a weekly Matrix ecosystem digest. Each Fgentic entry highlights one observable outcome and links a watchable artifact: a short demo, the browser demo, or a release. Do not submit a changelog, a roadmap promise, or a specification-only update.

Publication is an external-account action. A Matrix account holder submits the final text in #thisweekin:matrix.org, confirms that @this-week-in:matrix.org acknowledged it, and records the published post on issue #1617. Repository automation must not post under the maintainer's identity.

2. Friday task

  1. During the first-Friday preparation window in January, April, July and October, complete the competitive-landscape source refresh. The refresh is housekeeping, not itself a watchable outcome.
  2. By Thursday, choose one artifact published since the previous entry and verify it from a signed-out browser.
  3. Re-read the official TWiM guide and the room announcement for that week's deadline; the regular cutoff is around 16:00 Paris time, but the editors may change it.
  4. Replace every bracketed field in the five-line template. Keep the outcome factual, the limitation material, and the artifact directly watchable.
  5. Submit the five lines as one Matrix message beginning with a mention of the TWIM user, then require the helper-bot acknowledgement.
  6. After publication, add the matrix.org post URL, artifact URL, acknowledgement time, and submission time to issue #1617.

If no new watchable artifact exists, skip the week and record the gap honestly. Do not turn repository activity into an announcement merely to preserve a streak.

3. Five-line template

### Fgentic — the A2A appservice for Matrix
**This week:** [one observable outcome for Matrix operators or adopters].
**Watch:** [artifact name](https://example.com/watchable-artifact) — [what the artifact proves, in one sentence].
**Try or review it:** [one exact entry point](https://example.com/entry-point).
**Boundary:** Fgentic is experimental and pre-1.0; [one material limitation]. [Source and contact](https://github.com/fmind-ai/fgentic).

4. First four-Friday cadence

Issue #1617 owns the mutable evidence. These dates are the first acceptance window and remain fixed even if an editor publishes the corresponding digest later.

Submit by (Paris time) Required artifact Evidence recorded on #1617
2026-08-07 New demo, browser demo, or release since the previous published entry Bot acknowledgement and published post URL
2026-08-14 New demo, browser demo, or release since the previous published entry Bot acknowledgement and published post URL
2026-08-21 New demo, browser demo, or release since the previous published entry Bot acknowledgement and published post URL
2026-08-28 New demo, browser demo, or release since the previous published entry Bot acknowledgement and published post URL

5. Prepared first entry

This draft is source-ready for the first window, but the submitter must recheck every link and current-status claim before posting.

### Fgentic — the A2A appservice for Matrix
**This week:** Fgentic made its adopter path bridge-first: install the standalone Matrix-to-A2A appservice into a homeserver you already operate, while the full Kubernetes platform remains the reference distribution.
**Watch:** [v0.1.1](https://github.com/fmind-ai/fgentic/releases/tag/v0.1.1) — the current release and its SPDX SBOM provide an immutable artifact for evaluating the bridge boundary.
**Try or review it:** [the standalone bridge and out-of-tree agent-pack guide](https://fmind-ai.github.io/fgentic/extending-without-forking/).
**Boundary:** Fgentic is experimental and pre-1.0; the deterministic laptop demo proves transport rather than model quality. [Source and contact](https://github.com/fmind-ai/fgentic).