Skip to content
Docs/Glossary

What the words mean.

Every term explained three ways: in plain English, as it appears in Aether, and in technical detail for developers. Pick the one you need.

◉

Signal

02 · understand
Plain languageSomething happened.
Product meaningAn observed event from any connected source — page viewed, order completed, agent invoked a tool.
Technical meaningAn observation validated against the canonical event registry and accepted at /v1/batch.
○

Source

01 · connect
Plain languageWhere something happened.
Product meaningThe application, platform, device, provider, or agent a signal came from.
Technical meaningThe origin metadata attached to every canonical observation envelope.
⚙

Connection

01 · connect
Plain languageHow a system is linked to Aether.
Product meaningA connector, SDK, API, webhook, or import that brings activity in.
Technical meaningA managed connector or ingestion path with authorization, sync lifecycle, cursor state, and normalization.
⬡

Entity

02 · understand
Plain languageA person, agent, organization, system, or device.
Product meaningAnything Aether can resolve and build a Profile for.
Technical meaningA typed node in the tenant-scoped graph, resolved from identity evidence.
⬡

Profile

02 · understand
Plain languageEverything Aether knows about one person, agent, organization, or other entity.
Product meaningThe 360 view for a resolved entity.
Technical meaningA tenant-scoped resolved entity projection constructed from evidence and identity relationships.
↔

Relationship

02 · understand
Plain languageHow two things are connected.
Product meaningAn edge in the Graph — observed or inferred — with its evidence.
Technical meaningA typed, temporal graph edge produced by resolution and projected from the graph outbox.
→

Journey

03 · explore
Plain languageThe path that led to an outcome.
Product meaningAn ordered sequence of touchpoints in Journeys and Journey 360.
Technical meaningJourney construction over temporally ordered, linked signals; supports pause, resume, branch, and re-entry.
◈

Lens

03 · explore
Plain languageA perspective on the same information.
Product meaningA saved, combinable view that foregrounds identity, value, risk, geography, time, or agents.
Technical meaningA projection with semantic merge over the tenant graph; does not copy data.
◈

Syndicate

03 · explore
Plain languageA group that acts together.
Product meaningA relationship cluster across people, agents, and organizations.
Technical meaningA detected subgraph community with shared edges; currently direction, not a released capability.
⬡

Agent

04 · act
Plain languageSoftware acting on someone’s behalf.
Product meaningAn actor in Agents and Agent 360, with lineage and authority.
Technical meaningAn entity with lifecycle, parent/child lineage, delegated authority, and tool-call evidence.
↑

Value

04 · act
Plain languageWhat an outcome was worth, and what contributed to it.
Product meaningRevenue and economic activity linked to relationships, with attribution.
Technical meaningAttribution credits over journey touchpoints, joined to normalized financial events.
✓

Evidence

04 · act
Plain languageWhy Aether believes what it believes.
Product meaningThe observed, inferred, resolved, authorized, executed, verified, or measured state of a claim.
Technical meaningEvidence-state metadata on every edge and projection; inference is never stored as observation.
●

Outcome

04 · act
Plain languageWhat resulted.
Product meaningThe measured end of a journey, agent action, or campaign.
Technical meaningA terminal event or measured state linked back through journey and attribution edges.
Internal to public

Engineering terms, translated.

InternalProductPublic explanation
ObservationSignal / eventSomething happened
Identity stitchingProfile resolutionRecognize the same entity across systems
Graph projectionGraphConnect entities and activity
Canonical contractEvent / schema contractGive different systems a common language
Temporal graph queryTimeline / historyUnderstand how something changed over time
Attribution creditsValueUnderstand what contributed to an outcome
Agent lineageAgent relationshipsSee which agents created or directed other agents
Journey constructionJourneysSee the path that led to an outcome