Start with an operating model built for the work
An Eos Pack configures the records, navigation, layouts, dashboards, reports, Skills, Agents, and mobile experiences needed for a specific kind of work. Your organization starts with a coherent model and can still adapt it.
Records, experiences, and intelligence belong together
Operating records
Objects, fields, relationships, terminology, permissions, and reporting definitions establish what the organization can record and measure.
Configured experiences
Navigation, lists, page layouts, dashboards, forms, actions, and mobile placements put those records into the flow of work.
Governed intelligence
Skills give Agents controlled ways to work with Pack data. Agents arrive as reviewable drafts rather than silently activating themselves.
Start with a working vertical model
The first Eos Pack is available for restoration-contractor pilot organizations.
Restoration Contractors Pack
Configure Eos around restoration Jobs, site visits, field captures, readings, documentation requirements, exceptions, and human-approved evidence packages.
Packs do not fork Eos
The Pack uses the same metadata, access, reporting, Skill, Agent, and experience runtimes as the rest of Eos. Organization-specific changes can layer over packaged defaults without rewriting the Pack.
See how governed Agents workStart specific without getting trapped
A Pack supplies a tested starting structure. Organization-level metadata can change labels, navigation, layouts, fields, dashboards, reports, and policies while the package definition remains identifiable.
A Pack may include
- Standard-object extensions and custom objects
- List and record-page layouts
- Menu items, terminology, and dashboards
- Reports and aggregations
- Forms, actions, and mobile experiences
- Skills, draft Agents, and approval boundaries
See what the Pack would install before it changes the organization
Review the objects, screens, controls, and Agent boundaries against one representative job or engagement.