Builder

Create notice file

A practical next step after profile.md and aura.md: a public publisher can map what is safe for noticeboard screens, what needs more questions, and what technical setup is still unknown.

Profile Builder Aura Builder

Part A - basic public layer

Start with the public doorway: who the entity is, where it fits, and who can approve a notice before it appears on a screen.

Category Requested category Public name Place or service area Plain-language role Public profile.md path or link Who approves public notices?

Public contact preference

Use existing public contact Ask before displaying contact details No public contact on screens

Part B - advanced publishing choices

This section is a search map, not a promise. Tick useful possibilities, add better wording where needed, and leave uncertain items as questions.

Review rhythm

Public updates this entity might share

Other public update ideas

Theme families that might fit

Known local dates, seasons or global themes

Never publish by default

These are guardrails, not choices. The public noticeboard pipeline should exclude them unless a specific human approval process says otherwise.

Extra privacy boundaries for this entity Questions still needing real answers

Part C - technical pipeline

Technical setup can be left blank. This part is for the person setting up repositories, devices, screens, assets and sync rules.

Screen shapes to support

Device location IDs

Asset situation

Not sure yet Has brand assets Needs an asset pack Text-only first

Asset pack or folder notes Sync or repository notes