AEOS
--:--:--

Calendar

DisconnectedAvailable

Productivity · CalDAV / Google Calendar · v0.8.0 · manifest schema 1.0

The scheduling transport. Executive review cadence, workflow deadlines and approval SLAs all imply a calendar, and today those live only as relative labels inside their own modules. This connector is where they acquire real dates once a workflow can be scheduled rather than launched.

Last sync
—
Health
—
Rate ceiling
180/min
Webhooks
supported

Add to the estate and begin the authentication handshake. Every operation is a state transition inside AI-EOS — no external service is contacted.

Health

0/100

Not installed. Nothing is measuring it.

Authentication

Unconfigured
Method
OAuth 2.0
Credential
—
Last verified
never
Principal
—
Expires
Does not expire
Scopes held
0/2
Scopes
  • calendar.events
  • calendar.readonly
Handshake · OAuth 2.0
  1. 1.InitiateThe Hub prepares a OAuth 2.0 request for CalDAV / Google Calendar.
  2. 2.Supply client idexternalProvided on CalDAV / Google Calendar's authorisation screen, not in AI-EOS.
  3. 3.Supply client secretexternalProvided on CalDAV / Google Calendar's authorisation screen, not in AI-EOS.
  4. 4.Supply redirect uriexternalProvided on CalDAV / Google Calendar's authorisation screen, not in AI-EOS.
  5. 5.Supply scope grantexternalProvided on CalDAV / Google Calendar's authorisation screen, not in AI-EOS.
  6. 6.VerifyThe Hub performs one authenticated read to confirm the grant, then records the reference.

Nothing is contacted. The Hub stores no credential material — only a masked reference, the granted scopes and an expiry. There is no field on the auth record a secret could go in, which is a stronger guarantee than a policy of not putting one there.

Capabilities2

  • Create eventsevent.write

    Schedule a review or a deadline from a workflow.

  • Read availabilityevent.read

    Check a seat's availability before scheduling.

Modules request capabilities, never connectors. A capability offered by two connectors gives the requesting module a fallback it does not have to know about.

Usage · 24h

0
Calls
0
Records
0ms
Mean latency
0%
Error rate
180/min
Rate ceiling
declared by the manifest
0%
Peak usage
saturates at 80%
Peak consumption against ceiling

Event Subscriptions2

  • Workflow Blockedworkflow.blocked

    A workflow stalled on a dependency or an unapproved gate.

    Raised by workflows · see the fan-out chain

  • Approval Requestedapproval.requested

    A gate opened and is waiting on an executive seat.

    Raised by workflows · see the fan-out chain

Publisher

First party
Name
AI-EOS
Publisher ID
aeos
Platform vendor
CalDAV / Google Calendar
Support
operations@ai-eos.internal

Published by the platform itself. These manifests ship with the build rather than being fetched.

CalDAV / Google Calendar owns the platform this plugin reaches. AI-EOS authored the manifest.

Version and changelog

Up to date
Installed
0.8.0
Published
0.8.0
Minimum platform
1.0.0
Compatibility
Compatible
Manifest schema
1.0
First published
5 months ago

Requires platform 1.0.0 or newer. This build is 1.0.0.

  • 0.8.0minor · 5 months ago
    • Pre-1.0. Event read and write against CalDAV; free/busy resolution is not implemented.
    • Subscribed to workflow.blocked so a stalled workflow can hold a slot.

Permissions and scopes

viewer+

AI-EOS permissions are what this plugin may do insidethe platform, resolved against the API Gateway’s own table. Scopes are what the external platform is asked to allow. They are different systems and neither substitutes for the other.

  • workflow:read4 roles

    Workflows, stages, tasks and approval gates.

  • company:read4 roles

    Companies, departments, executives and the knowledge graph projection.

Requested external scopes
  • calendar.events
  • calendar.readonly

Dependencies0

Declares no dependencies. It can be installed against an empty estate.

Whether each is satisfied is resolved against the live estate at install time, not here.

Security

Authentication
OAuth 2.0
Credential storage
Never stored
External scopes
2
AI-EOS permissions
2
Minimum role
viewer
Inbound deliveries
Signature verified
Tenant isolation
Installation state is tenant-scoped

A plugin is a data literal. Nothing in the marketplace executes plugin code, and a plugin cannot bypass the Authentication Manager, the Integration Hub, the API Gateway or a permission check, because it has no code path — the host performs every transition.

The auth state type has no field a credential fits in, so the guarantee is enforced by the type checker rather than by convention.

Privacy

Data leaving AI-EOS
1 capabilities
Data entering AI-EOS
1 capabilities
Modules served
3
Event topics received
2

Direction is declared per capability, so what this plugin can send and what it can receive are both enumerable rather than a matter of trust. It reaches only the modules listed above, and only through capabilities the Integration Hub resolves.

Documentation2

Webhook Manager0

No endpoints registered. Install a connector that supports webhooks to open an inbound path.

Logs1

  • Registry—Not installed. The Hub holds a manifest for this connector but no connection.

Roadmap

  • Scheduled workflow instantiation, which the Workflow Engine already anticipates
  • SLA timers on approval gates backed by real dates

What this connector would gain next. Mirrors the Future Integrations list every module carries in the Navigator registry.