[Components](https://oods-foundry.com/components) / lifecycle

# ArchiveEvent

Describes an archive event with its recorded timestamp.

Generated from @oods/foundry 0.10.1

- Categories

  lifecycle

- Contexts

  timeline

- Readiness

  `react-and-vue`

## Playground

This component's contract doesn't list typed props, so the playground shows its documented example.

Documented example `ArchiveEvent` : mount and declared input triggers, Archive and restoration instants remain distinct and ordered as declared; valid dates render stable UTC time, missing dates remain disclosed. Actor and reason are visible when supplied..

The render follows the page's theme switch: light, dark or high contrast. Both frameworks render the same example.

The real ArchiveEvent, live

React

## Archive events

1. **Archived**

   Sep 1, 2026, 12:00 PM

   Actor: operator-1

   Reason: Duplicate record

2. **Restored**

   Sep 2, 2026, 12:00 PM

Vue

## Archive events

1. **Archived**

   Sep 1, 2026, 12:00 PM

   Actor: operator-1

   Reason: Duplicate record

2. **Restored**

   Sep 2, 2026, 12:00 PM

## Code

The documented example. HTML is the markup the React component renders for it, which @oods/component-styles styles.

**React**

```
import { ArchiveEvent } from '@oods/components-react';
import '@oods/component-styles/css';

export function Example() {
  return (
    <ArchiveEvent
      archivedAt="2026-09-01T12:00:00Z"
      restoredAt="2026-09-02T12:00:00Z"
      archivedBy="operator-1"
      reason="Duplicate record"
    />
  );
}
```

## Props, slots and events

Contract version 1.1.0. Types are from the React declarations in @oods/components-react.

Props

| Prop | Type | Required | Documented example |
| - | - | - | - |
| `title` | `string \| undefined` | no | |
| `archivedAt` | `string \| null \| undefined` | no | `2026-09-01T12:00:00Z` |
| `restoredAt` | `string \| null \| undefined` | no | `2026-09-02T12:00:00Z` |
| `archivedBy` | `string \| null \| undefined` | no | `operator-1` |
| `reason` | `string \| null \| undefined` | no | `Duplicate record` |
| `showActor` | `boolean \| undefined` | no | |
| `showReason` | `boolean \| undefined` | no | |

### Slots

none

### Events

none

## States

empty, populated

## Accessibility

- Role

  `article`

- How it gets its name

  `aria-label` on `[data-oods-component="ArchiveEvent"]`

### Keyboard

The contract lists no keyboard behaviour.

### Obligations in the contract

- Visible text exposes values without relying on color
- Named semantic container or noninteractive span

Archive and restoration instants remain distinct and ordered as declared; valid dates render stable UTC time, missing dates remain disclosed. Actor and reason are visible when supplied; with no archive or restore recorded the card renders nothing (s223-m01). metadataField and restorationMetadataField are consumed unbound, matching the retained renderer; metadata inspection is not claimed.

## Tokens

The token roles this component reads.

- `surface.panel`
- `text.body`

## Readiness

The evidence recorded for this component, with its label.

`react-and-vue`: catalog_list gives this label when the React and Vue components have complete readiness evidence, but the sweep's generated apps don't use the component in both.

Readiness evidence

| Evidence | React | Vue |
| - | - | - |
| state | implemented-evidence-complete | implemented-evidence-complete |
| versioned contract | passed | passed |
| target implementation | passed | passed |
| package export | passed | passed |
| public declaration | passed | passed |
| dependency closure | passed | passed |
| framework scenario | passed | passed |
| accessibility | verified | verified |
| interaction | not-applicable | not-applicable |
| visual themes | verified | verified |

ArchiveEvent presents declared trait values and owns no focusable control or consumer action.

## Use your own

You can replace this component with your own React or Vue component. Map it, and generated code imports yours at the exact version you name. A contract report, run in a real browser, lists what your component met, what it didn't, and what wasn't checked.

The `component_map` call, with the parts in angle brackets yours to fill:

```
{
  "action": "create",
  "apply": true,
  "externalSystem": "<your design system>",
  "externalComponent": "<YourArchiveEvent>",
  "oodsTraits": [
    "<trait names>"
  ],
  "substitution": {
    "component": "ArchiveEvent",
    "react": {
      "package": "<your-package>/react",
      "version": "<exact version>",
      "export": "<YourArchiveEvent>"
    },
    "vue": {
      "package": "<your-package>/vue",
      "version": "<exact version>",
      "export": "<YourArchiveEvent>"
    }
  }
}
```

## How this page was made

Generated at build from the published data, each source with the hash of what was read. [The page's manifest](https://oods-foundry.com/components/archive-event/manifest.json).

- **Contract**: `@oods/component-contracts@0.10.1 componentContracts.ArchiveEvent` `sha256:29bf0407c8ad…`
- **Documented example**: `@oods/component-contracts@0.10.1 sharedScenarios ArchiveEvent` `sha256:b620aae9d539…`
- **Catalog entry (catalog_list)**: `generated/0.10.1/system/catalog.json ArchiveEvent` `sha256:900797a89e6e…`
- **React readiness**: `@oods/components-react@0.10.1 readiness ArchiveEvent` `sha256:3e14d9be0a84…`
- **Vue readiness**: `@oods/components-vue@0.10.1 readiness ArchiveEvent` `sha256:66c47dd5e723…`
- **Prop types**: `generated/0.10.1/components/prop-types.json ArchiveEvent` `sha256:b9384a14ac7a…`