About

Known limitations

What this site cannot yet do, what it deliberately withholds, and where the record is thinner than it looks. Updated with each release; the date of this page's last change is shown at the bottom.

1. How the answer box states votes

The answer box on a search page asks a local AI which City records answer your question. No sentence of the answer is written by an AI: code writes the sentences from the fields of the records the AI chose (the vote, a mover or seconder, a tally, a date, a dollar amount, a job title, and a stage such as draft or proposed), says when a record is from draft minutes, and ends the sentences with footnotes that lead to their records. A motion whose printed result contradicts its printed vote count is described as unresolved, with the reason, and not as passed or failed. The records' own words, as printed, are under "Show the exact wording". The AI can still choose a record that does not answer your question. A vote, a mover or seconder, a tally or a dollar amount tied to an action is shown as the structured record stores it, with the meeting it came from and a link to that meeting. Those rows are copies of the archive's records; they are not independently checked against the minutes unless the row says so.

2. Names and titles

  • Council titles (Mayor, Deputy Mayor, District seat) are shown as they stood on the meeting date, from a dated roster built from the minutes. Twenty-two of 626 title labels in the harvested minutes still disagree with that roster; twelve of them cannot be settled from any document we hold, and those rows carry a title_unverified_gap flag.
  • A mover or seconder read from a transcript is marked identity: inferred from transcript. Only rows read from the minutes are marked as such.
  • Where the record could not resolve a person (two names in one field, or a field that holds a speaker label instead of a motion), the row says not resolved in the record and names the parse flag. As of September 18, 2026, 105 vote rows have a motion field that holds the mover's name rather than the motion text; the motion text for those rows is shown as unresolved until it is restored from the minutes.
  • A meeting page states who attended only from the City's minutes: the roll the Clerk records at the head of the minutes, kept apart from who is named on a ballot later in the meeting. Where the roll as read leaves out a member who later voted, the roll is not stated. Where no minutes are on file, attendance is not stated.

3. Source corrections still open

An attribution check comparing the knowledge base against the minutes has 13 open findings (title, person or motion-text mismatches) and two further items traced to their source. Corrections are applied only with the site owner's decision and through a journalled, reversible change; until then the affected rows are shown with their qualifiers, not silently fixed. The corrections page explains how to report an error.

4. Coverage of the record

  • Minutes are harvested from the city's CivicClerk portal. Votes, results and attendance come only from the City's minutes; a meeting whose minutes are not yet published shows none.
  • Meetings whose recording was a placeholder or was superseded are held aside and are not in the search index; their meeting pages say so.
  • AI-written topic, people and period summaries are not shown and are not evidence: the answer box does not use them.

5. Features not yet working

  • Email digests: the subscription form works and confirmations are recorded, but no mail is sent until a mail provider is connected. A confirmation link that never arrives means this, not a mistake in your address.
  • District lookup by address: the page lists the districts but cannot yet place a street address in one.
  • About 123 land-use topic descriptions were generated automatically and have not yet been rewritten from the record.

6. Accessibility

An accessibility review against WCAG 2.1 AA is scheduled before public launch; exceptions found will be listed here.

7. What this site is not

It is not the official record. The official record is the minutes and the recordings the City of Cocoa publishes. Every page links back to its source so you can check.

Last changed: September 22, 2026. Methodology: how the data is collected and verified. Errors: corrections and contact.