The company behind Lucas and Sentinel.

Residents move across jurisdictions. Agencies still need to control their own public information and handle incoming reports through their own responsibilities.

Lucas is the citizen experience. Sentinel is the department workspace. The aim is a shared network without blurring those distinctions.

The team works across product direction, application development, interface decisions, and department evaluation. A product's value depends on how it works in practice and how clearly its limits are explained.

Jacob Brink (Jacob Dawson Brink) leads the business and product direction. Trey Everett Hugan is the technical co-founder and Chief Technology Officer. Their work on Lucas and Sentinel sits within Detailr Corp.

Detailr Corp is a Delaware corporation. Lucas and Sentinel are product names, not police departments or emergency service providers. The consumer policies identify the operator and the scope of the service.

Public information is most useful when people can understand it and know how to contribute relevant context. A notification can open that exchange, but the detail, recipient and subsequent review determine whether it remains coherent. Lucas and Sentinel are being developed around that relationship.

The motivation is practical: help participating departments communicate with a public whose daily life crosses municipal boundaries, and help residents recognize an appropriate next step. The ambition is a more useful connection between people and agencies, supported by clear roles rather than a claim that one product replaces every existing system.

We favor recognizable sources, community participation and explanations that people can use. A resident should not need a technical background to understand what an agency is asking or what a privacy setting changes. An evaluator should be able to inspect the actual workflow rather than rely on a sweeping promise.

Our vision is a network that becomes more useful through relevant participation while preserving each department’s responsibilities. That remains a direction for the work, not a claim of established national reach. We intend to earn confidence through the product’s behavior, the clarity of its public information and the quality of what can be demonstrated.

A department can publish a short message, but a resident may need more detail before knowing what it means or whether an observation is relevant. The resident can have useful information without knowing which agency should receive it. Lucas and Sentinel are being developed around that exchange.

Lucas focuses on the person following participating departments and reading their updates. Sentinel focuses on the department publishing information and reviewing what comes back. Keeping those audiences distinct helps the team ask better questions about each task instead of presenting the same interface to everyone.

The products belong to Detailr Corp. Their public explanation should identify that operator, distinguish current capabilities from goals and give people a clear place to ask a question. That is the basis for a credible introduction to a developing platform.

Jacob Brink (Jacob Dawson Brink) leads the company’s product and business direction. His work includes defining priorities, reviewing the resident and department journeys, coordinating development and preparing agency discussions. Trey Everett Hugan is the technical co-founder and Chief Technology Officer, working on the applications and the technical decisions that connect them.

The roles meet in practical decisions. A proposed public request needs an understandable resident experience and a department workflow that can support it. A feature that changes what can be submitted also changes the explanation users need before sending it.

The leadership profiles describe those current responsibilities and the relevant experience the team has supplied. Both roles combine planning with continuing review as the applications develop.

A larger network can create more opportunities for a relevant observation to reach an agency, but size alone is not the purpose. Participation needs a clear source, an appropriate recipient and a review process that the department understands.

That is why evaluation begins with specific tasks and operating questions. We want the public explanation, product behavior and staff process to fit together before a broader promise is made. Useful feedback can change the design, the priorities or the scope of a proposed rollout.

Our mission page sets out the intended direction. The product and trust pages explain how to assess the current offering. For a department, the next step is a conversation about its needs and the evidence required for an evaluation.