A communication problem with two sides
Lucas and Sentinel begin with a practical exchange: a department has information to share, and a resident may have an observation that helps the department understand a situation. Publishing a message is one part of that exchange. Making the request understandable and organizing what comes back are separate tasks.
The resident needs to recognize the source, understand the place and time, and know what action is appropriate. The department needs to review submissions, understand their context and decide who handles the next step. That distinction shapes the two products. Lucas is the resident experience; Sentinel is the department workspace.
October 31, 2026 — more useful local source guidance
The public information resources expanded to ten East Bay city guides and a regional official-source directory. The purpose was to help readers distinguish police activity information, reporting channels and emergency-warning subscriptions instead of treating them as interchangeable.
The local guides explain differences in the official resources available in each place. They also distinguish those resources from Lucas participation. Inclusion in a directory is a source reference, not a statement that a department uses the platform.
November 2, 2026 — clearer leadership and responsibilities
The company and founder information was updated to make responsibility for the products easier to identify. Jacob Brink leads product and business direction as Chief Executive Officer. Trey Everett Hugan leads technical work as technical co-founder and Chief Technology Officer.
For Jacob, product direction includes reviewing the resident and department journeys, setting priorities and preparing agency discussions. Trey connects those priorities with application development and technical decisions. Their individual profiles explain those responsibilities in more detail.
Source: Jacob Brink · Trey Everett Hugan
What this history establishes
These milestones document the development of the public explanation and resources around Lucas and Sentinel. A website publication date is different from a company incorporation date, an app release or an agency deployment. This history does not treat one as proof of another.
The work remains focused on practical evaluation: which tasks the products support, how a department would operate them, and what residents need to understand before responding. Current participation and available features should be established directly rather than inferred from an illustration or directory entry.
Source: Department evaluation guide
The next chapter is grounded in actual use
The next useful milestones are ones that can be demonstrated: a workflow evaluated by the people who would operate it, a clear resident journey and feedback that leads to a concrete improvement. Verified findings can be added as that work occurs.
For an agency, an evaluation can follow a fictional request from publication through the review and assignment of a response. The team can discuss the current product and the operating questions that matter to that department. Residents should continue using official local warning channels and call 911 for an emergency.
Source: Discuss an agency evaluation · Company mission

