List Cloud accounts

When Truto actually read this object from the provider, in UTC ISO 8601 with the offset present. Not when the request was made and not a provider timestamp. Drives consumer staleness rules.

Truto's stable unified identifier for this object. Opaque; use provider_ref to address the object in the provider's own console or API.

The account, subscription or project name.

The provider's own type string, unmodified -- for example 'AWS::S3::Bucket', 'aws_iam_role', 'Microsoft.Sql/servers'. Used for display and drill-down.

Which cloud this object was read from.

The provider's own unbroken identifier, passed through verbatim -- a full ARN, resource id or self-link. Never truncated, prefixed or normalised. This is the customer-facing key used to find the object in the console.

Lifecycle state of the account. On AWS this is read from Account.State, not the retired Account.Status, which carried three values and no CLOSED.

When the account was genuinely created. On AWS this needs a separate account-service call and is null unless that call was made; it is never back-filled from joined_at.

The account's registered contact address, where the provider exposes it.

The full hierarchy path from the organisation root down to this account, as a single string. This is the best available classification input, because customers usually signal which accounts are production through the hierarchy. On AWS it is materialised directly from Account.Paths rather than reconstructed by a recursive parent walk.

All hierarchy paths for this account, where a provider allows more than one. Never collapsed to a single value.

Whether Truto currently holds working credentials for this account. False for accounts discovered in the organisation but not reachable -- the coverage gap the customer needs reported, and the reason enumeration must not be limited to connected accounts.

When the account joined the organisation. Exposed under its own honest name rather than as created_at: for an invited account this is the invitation acceptance date, which can be years after the account was created.

How the account entered the organisation, as the provider reports it.

The organisational unit, folder or management group directly above this account.

Where the object is. A compliance answer in its own right, not metadata. The literal string 'global' is emitted for genuinely global resources (for example IAM, or a GCP VPC network) rather than guessing a region. Never invented: where the provider does not return a location and none can be derived, the collector's queried region is used and that substitution is recorded in unreadable_fields.

Raw data returned from the remote API call.

Key-value pairs exactly as the customer set them: no case folding, no key or value normalisation, no merging of separate provider concepts. Present on every object because tags are the primary input for environment classification. An empty object means the object carries no tags; tags that could not be read are recorded in unreadable_fields instead.

Per-object list of the fields that could not be read, and why -- the brief section 8.4 answer, chosen over per-field sentinel values. Each entry is an object with 'field' (the property name on this resource), 'reason' (a reason code) and an optional human-readable 'detail'. Reason codes: not_supported_by_provider, not_configured, permission_denied, not_collected, collection_error, partially_collected. An empty array means every property on this object was read successfully. A property absent from this array and null in the payload means the provider genuinely returned no value, which is different from 'we could not look'.