This living article explains how to continue the Village Hall event-maintenance work with Codex or by following the same process manually.
Access required
- Codex desktop installed locally for the assisted workflow.
- The ChatGPT Chrome extension enabled.
- Chrome signed into the FRVH WordPress dashboard through the frvh-login address.
- WordPress Editor access to Events, Organisers, Knowledge Base and Gravity Forms entries.
- Google Calendar read access for Freshfield Hall, Peter Griffits Hall and RBL Committee Room.
- Notion access to Event Listings & Hirer Tracking.
WordPress connection
No separate WordPress.com site connection is needed. Codex can use an existing signed-in Chrome session, but access or sign-in is not permission to use it. The operator must have the necessary permissions, must never give passwords to Codex, and must explicitly approve each browser or account action.
Authoritative sources
- The hall manager confirms whether a booking may be advertised.
- Google Calendar supplies dates, halls, booking times and operational notes.
- The Booking Form is only the initial hire request.
- Public Event Details supplies the approved public copy, categories, contacts and featured image.
Non-negotiable working rules
- Show only the three hall calendars.
- Open every more overflow control before deciding an event is absent.
- Never publish a booking marked PROV, No Class or Cancelled.
- If confirmation is unclear, contact the hall manager.
- If a confirmed public booking lacks Public Event Details, ask the hirer to complete that form before publication.
- Use the newest suitable past event as a recurring-series reference.
- Keep only one occurrence featured unless specifically instructed otherwise.
- Use generic Private Event listings for private bookings and never reveal the hirer or purpose publicly.
- Verify WordPress after every batch and update Notion and this article.
Living Codex seed document
Copy the following into a new Codex task when handing the work over. Update this seed whenever the process changes.
I am maintaining events for Forest Row Village Hall. Operate in read-only mode by default. Do not open or navigate Chrome, access an account, or make a change unless I explicitly approve that exact system, action and destination. A signed-in session is not authorisation. For external communications, show me the complete text, sender, recipient or Page/profile, destination, links and attachments and wait for separate explicit approval. When a browser result is ambiguous, record it as unverified. After approval to review, show only Freshfield Hall, Peter Griffits Hall and RBL Committee Room in Google Calendar. Show only Freshfield Hall, Peter Griffits Hall and RBL Committee Room. The Booking Form is only the hall-hire request; use Public Event Details for public copy and images. Publish only after hall-manager confirmation and receipt of Public Event Details. Never publish anything marked PROV, No Class or Cancelled. Open every Google Calendar “more” overflow before deciding a booking is absent. Use the newest suitable event as a recurring-series reference, keep only one occurrence featured, protect private hirer information, verify every batch, and update Event Listings & Hirer Tracking in Notion plus the FRVH workflow documentation.
Manual fallback
The same checks can be completed without Codex by following the Create a New Event article. Codex accelerates comparison, duplication, verification and documentation, but it does not replace access permissions or human confirmation from the hall manager.
Approval and change control
- Codex works in read-only mode by default. Browser access, a connector and an existing signed-in session are not authorisation to act.
- State the exact proposed system, action and destination, then wait for explicit approval. Approval is limited to that scope.
- Before email, Facebook or any external communication, show the complete final text, sender account, recipient or Page/profile, destination, links and attachments. Obtain separate explicit approval immediately before sending or publishing.
- Record ambiguous browser results as unverified and never claim success without confirmation.
Listing planning cycle
Maintain listings in three blocks: September–December, January–April and May–August. Prepare each block shortly before it begins, using the newest suitable event as the duplication reference.
Monthly review checkpoint
- On the first working day of each month at 09:00, a reminder asks Nicolas whether to approve a read-only calendar review.
- The reminder does not open a browser, access an account, perform a scan or make a change.
- After approval, compare WordPress with the three hall calendars and report new or missing bookings, cancellations, venue or time changes, PROV items, missing Public Event Details, featured totals and outstanding follow-ups.
- Present proposed changes separately and wait for explicit approval before making them.
Keeping this document current
Treat this as the website copy of the evolving Codex working document. Update it alongside the Dropbox workflow file whenever a new rule, exception or access requirement is discovered.
