Add TIP-0006: Tari Announcements ChannelCreate TIP-0006_tari_announcements_channel.md

[xt1085]

Description

Proposes a new Process TIP (P-TIP-PROC-6) to establish a dedicated, read-only "Tari Announcements" channel for structured official updates, organized by category and posted on
a fixed cadence, separate from the main community group.

Motivation and Context

Official updates are currently buried among thousands of daily messages. New members can't quickly see project status, and media/partners have no clean, authoritative source.
Suggested by Simon Hill in the community chat.

How Has This Been Tested?

N/A. Community process proposal, no code or consensus changes.

[gemini-code-assist]

Code Review

This pull request introduces a new proposal, P-TIP-PROC-6, which outlines the creation of a dedicated, read-only "Tari Announcements" channel to streamline official updates. The review feedback suggests formatting improvements to align with standard TIP guidelines, specifically recommending that the TIP ID in the metadata table link to its header anchor, reminding the author to register the document in src/SUMMARY.md, and requesting a pull request link in the Change History section.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

To maintain consistency with other Tari Improvement Proposals (such as TIP-0001, TIP-0002, and TIP-0003), the TIP field in the metadata table should be a markdown link pointing to its own header anchor. Additionally, please remember to register this new TIP in src/SUMMARY.md so that it is included in the mdBook build.

Suggested change

	| TIP | P-TIP-PROC-6 |
	| TIP | [P-TIP-PROC-6](#p-tip-proc-6-tari-announcements-channel) |

[gemini-code-assist]

According to the TIP-0001 specification (under the 'Change History Section' guidelines), each entry in the Change History must include a link to the pull request where the discussion and approval took place. Please add a placeholder or the actual pull request link to this entry.

Suggested change

	* Document Created.
	* Document Created.
	* [Pull Request #<PR_NUMBER>](https://github.com/tari-project/rfcs/pull/<PR_NUMBER>)