Restricted realization evidence register
This public register records only disclosure-safe status. Detailed source identity, revision, excerpts, paths, and implementation findings remain in the owner-approved restricted evidence location.
| Evidence ID | Capability | Evidence type | Public disposition |
|---|---|---|---|
RAS-01-A | retain governed content | requirements and static implementation trace | assessed; details withheld; no tested/deployed claim |
RAS-01-B | derive content from a retained source | requirements and static implementation trace | assessed; disagreement retained privately; no tested/deployed claim |
RAS-01-C | allocate retained content to a context | requirements and declared structure | assessed; reachability and availability unknown |
RAS-01-D | assemble governed retrieval context | requirements and partial static implementation trace | assessed; completeness and availability unknown |
RAS-01-E | consolidate conversation history | requirements and declared structure | assessed; producer, tests, and availability unknown |
RAS-01-F | maintain personal glossary terms and organizing labels | requirements assessment | assessed; public realization not confirmed |
RAS-01-G | detect candidate glossary terms | requirements assessment | assessed; static implementation review continues privately |
RAS-01-H | govern and apply AI-assisted labels | requirements assessment | assessed; implementation reachability not publicly claimed |
RAS-01-I | apply contextual classification | requirements assessment | assessed; implementation reachability not publicly claimed |
RAS-01-J | maintain deliberate knowledge notes | requirements and realization-pattern assessment | assessed; code reachability not yet claimed |
RAS-01-K | maintain owner-authored profile knowledge | requirements and partial static implementation trace | basic owner profile fields and updates were identified; the richer versioned owner-authored knowledge model was not confirmed |
RAS-01-L | maintain and resolve evidence-backed profile assertions | requirements and planned/negative static assessment | profile-item and evidence surfaces are described as planned; no reachable assertion persistence, confirmation, dispute, or resolution lifecycle was confirmed |
RAS-01-M | apply action-intent labels | requirements and partial static implementation trace | owner-scoped action-label vocabulary CRUD and assignment to notes or captured storage items were identified; downstream handling execution was not confirmed |
RAS-01-N | invoke governed actions and run background operations | requirements and workflow-specific static implementation trace | one authenticated workflow execution path records steps and outputs; a generic action registry and durable background-operation lifecycle were not confirmed |
RAS-01-O | configure execution policy | requirements and placeholder/negative static assessment | the actions/skills surface is read-only and behavior controls are local presentation state; no durable generic execution-policy lifecycle was confirmed |
RAS-01-P | plans, plan activation, projects, routines, and routine runs | requirements and partial static implementation trace | objective, plan, activation, project and routine persistence paths were identified; no separate routine-run lifecycle was found |
RAS-01-Q | tasks, task collections, and reminders | requirements and static implementation trace | owner-scoped task, task-list and reminder CRUD plus due-reminder processing and recurrence updates were identified; no tested/deployed claim |
RAS-01-R | workflow packages, installed workflows, workflow runs, and results | requirements and static implementation trace | package catalog, installation, trigger, run, step and output records plus a manual server-run path were identified; scheduler and production state remain unconfirmed |
RAS-01-S | owner attention items and update lifecycle | requirements and static implementation trace | update creation, read, pin, dismiss, response and reminder-produced update paths were identified; current PIOS completed-work and History contracts were not confirmed |
RAS-01-T | source registration, import sessions, and source-promotion status | requirements and planned/negative static assessment | the System import surface is a future placeholder referring to future source/run records; no reachable registration, import-session, or promotion lifecycle was identified |
RAS-01-U | operational run and import inspection | requirements and partial static implementation trace | a read-only panel projects retrieval logs and storage-job state, timing and errors; import runs, authority, outputs, retries and full evidence linkage were not confirmed |
RAS-01-V | export-bundle composition and package validation | requirements and partial client-side export trace | an authenticated browser export builds selected JSON-LD, JSONL, Markdown, file-manifest and checksum content; completeness, independent validation and migration-grade behavior were not confirmed |
RAS-01-W | bundle restore | requirements and planned/negative static assessment | the product surface states that import from an export archive is planned; no restore, conflict-disposition, projection-rebuild or restore-report path was identified |
RAS-01-X | destination connector reauthorization | requirements and bounded negative static assessment | no destination credential, consent, scope-validation or connector-reactivation path was identified in the assessed portability and System surfaces |
RAS-01-Y | governed capture submission and pending reconciliation | requirements and partial static implementation trace | authenticated browser capture creates linked storage/note records, applies action labels and may create an instruction update; pending-capture reconciliation was not identified |
RAS-01-Z | onboarding journey, environment preparation, and first entry | requirements and partial static implementation trace | assessed; documented end-to-end journey not confirmed; no tested/deployed claim |
RAS-01-AA | personal AI identity and interaction preferences | requirements and partial static implementation trace | assessed; some interface state is not shown to be durably governed; no tested/deployed claim |
RAS-01-AB | first-use orientation | static implementation trace | bounded explanatory surface identified; not evidence of the broader onboarding journey or production availability |
RAS-01-AC | owner Role definition and hierarchy | requirements and static implementation trace | create, revise, archive, and relationship paths assessed; no tested/deployed claim |
RAS-01-AD | owner operating Mode definition | requirements and static implementation trace | create, revise, and archive paths assessed; some related attachment/activation paths remain incomplete |
RAS-01-AE | active personal context | requirements and partial static implementation trace | selected Role/Mode filtering state assessed; complete Core-backed lifecycle not confirmed |
RAS-01-AF | Role outward intent | requirements and partial static implementation trace | intent control assessed; access enforcement and publication are not established |
RAS-01-AG | Role-scoped outward representation | requirements assessment | assessed; relevant implementation reachability not confirmed |
RAS-01-AH | observed-pattern detection and lifecycle evaluation | requirements and declared/disabled structure assessment | assessed; no reachable active job, passing tests, deployment, or production behavior confirmed |
RAS-01-AI | outcome goals, directional objectives, and success targets | requirements and static implementation trace | bounded create/read/update paths and declared relationships assessed; target-achievement evaluation not confirmed; no tested/deployed claim |
RAS-01-AJ | measurement definitions and metric observations | requirements, declared structure, and partial static implementation trace | definition management assessed; observation structure found; reachable observation writer, tests, deployment, and production behavior not confirmed |
RAS-01-AK | outward sharing, publication, access, discovery, and usage rights | bounded negative static search | searched public-asset and exposure-model identifiers were not found; no implementation, test, deployment, or production claim |
RAS-01-AL | structured reviews and reflective assessments | requirements and partial static implementation trace | manually dispatched weekly review-note generation assessed; scheduled trigger, complete structured review semantics, tests, deployment, and production behavior not confirmed |
RAS-01-AM | human contact profiles and contact points | static implementation trace | owner-scoped profile and contact-point management paths assessed; verification, tests, deployment, and production behavior not confirmed |
RAS-01-AN | personal relationship context | requirements, declared structure, and partial static implementation trace | free-text relationship labeling assessed; richer origin, trust, consent, shared-history, and lifecycle behavior not confirmed |
RAS-01-AO | agent definitions, runtime roles, and definition synchronization | bounded negative static search | no named canonical agent-profile or runtime-target model identified; no implementation, test, deployment, or production claim |
RAS-01-AP | outward agent identity and owner-representative conversation | requirements and bounded negative/partial static assessment | personal-AI presentation and Role intent surfaces exist, but outward identity enforcement and AI-representative conversation were not identified |
RAS-01-AQ | collaboration channels, discussion threads, and attributed messages | requirements and partial static implementation trace | channel-like chat filters and owner-to-assistant message flow were identified; linked-thread lifecycle, participant/agent attribution, tests, deployment, and production behavior were not confirmed |
RAS-01-AR | task-scoped execution workspace | bounded negative static search | no named execution-workspace model or lifecycle was identified; no implementation, test, deployment, or production claim |
RAS-01-AS | personal conversation history | requirements and partial static implementation trace | one owner-linked history, source-aware entries, filter links, session markers, bounded context assembly, and a read-only history view were identified; complete provenance, correction, import, test, deployment, and production behavior were not confirmed |
RAS-01-AT | owner access paths and personal interface roles | requirements assessment | interface requirements were assessed, but no complete access-path registry, assurance lifecycle, fallback verification, tests, deployment, or production behavior was confirmed |
RAS-01-AU | personal reading queue | requirements and partial static implementation trace | retained article listing, read-state update, local saved state, presentation and AI-topic requests were identified; admission, completion, durability and topic-membership gaps remain; no tested/deployed claim |
RAS-01-AV | authorized device cache and selected offline content | no relevant realization confirmed | assessed application evidence did not establish the current PIOS device-cache or offline-retention contracts; availability remains unknown |
RAS-01-AW | operation resource-cost estimation, reservation, and reconciliation | requirements and bounded negative assessment | retrieval token-budget requirements were identified, but no generic cost-estimate, reservation, spend-accounting or resource-reconciliation realization was confirmed |
RAS-01-AX | candidate source discovery | bounded negative path assessment | no candidate-discovery, sitemap-discovery, feed-discovery or source-probing realization was identified; existing source/import structures do not establish discovery |
RAS-01-AY | owner implementation documentation and knowledge-layer integrity | bounded negative path assessment | no owner implementation-documentation lifecycle or knowledge-linting realization was identified; ordinary application documentation and code lint configuration do not establish these capabilities |
RAS-01-AZ | personal Meaning and evidence-linked Learning | requirements and bounded negative static assessment | generic meaning language and a learning-labelled operating context were identified, but no Cognitive Memory object, lifecycle, confirmation, recall, test, deployment, or production realization was confirmed |
RAS-01-BA | derived-representation lifecycle | requirements and retired-schema static assessment | an early note-embedding shape was identified and later removed; no retained writer, registry lifecycle, replacement/revocation path, test, deployment, or production realization was confirmed |
RAS-01-BB | working-artifact promotion to canonical state | bounded negative static search | no named canonical-home, promotion-boundary, workspace-promotion, working-copy, or promoted-artifact realization was identified; no test, deployment, or production claim |
RAS-01-BC | daily and higher-period History compilation | partial static summary-producer trace | daily and scheduled weekly/monthly/yearly summary producers were identified; canonical event-spine linkage, complete source provenance, curated History manifests, tests, deployment, and production behavior were not confirmed |
These entries are not public realization confirmations and must not be used to claim compatibility or availability.