No English page yet. Showing the Japanese source.
GROK：検索・記憶・出典の対応付け
記事状態: 公開 · 最終確認: 未確認
要点
This mapping binds xAI Collections, Collections Search, Files and ZDR to the existing CORE-02 contract. It does not treat collection membership, an API-key permission, an application-supplied metadata filter, a citation URI or a nominal context window as proof of authorization-before-retrieval, source freshness, answer faithfulness or durable memory correctness.
現在の判断
This mapping binds xAI Collections, Collections Search, Files and ZDR to the existing CORE-02 contract. It does not treat collection membership, an API-key permission, an application-supplied metadata filter, a citation URI or a nominal context window as proof of authorization-before-retrieval, source freshness, answer faithfulness or durable memory correctness.
どこまで当てはまるか
This mapping binds xAI Collections, Collections Search, Files and ZDR to the existing CORE-02 contract. It does not treat collection membership, an API-key permission, an application-supplied metadata filter, a citation URI or a nominal context window as proof of authorization-before-retrieval, source freshness, answer faithfulness or durable memory correctness.
No xAI API key, team, Console, collection, file, model or SDK process was operated. Existing OpenFGA/LlamaIndex/Mem0/Gemini UI results remain first-party evidence for their original scopes and are not Grok observations.
詳しく理解する
Product Mapping — Grok / CORE-02 Retrieval, Memory and Source Binding
MAPPING_ID: PM-GROK-CORE-02-v0.1
PRODUCT_MAPPING_ID: PM-GROK-CORE-02-v0.1
PROVIDER: Grok / xAI
CORE_PACKET: PKT-GEMINI-A-CORE-02-v0.1
STATUS: PUBLIC_MAPPING_AUDITED / LIVE_PROVIDER_AND_TENANT_PROFILE_PENDING
AS_OF: 2026-09-12
LAYER: Product Mapping
1. Boundary
This mapping binds xAI Collections, Collections Search, Files and ZDR to the existing CORE-02 contract. It does not treat collection membership, an API-key permission, an application-supplied metadata filter, a citation URI or a nominal context window as proof of authorization-before-retrieval, source freshness, answer faithfulness or durable memory correctness.
No xAI API key, team, Console, collection, file, model or SDK process was operated. Existing OpenFGA/LlamaIndex/Mem0/Gemini UI results remain first-party evidence for their original scopes and are not Grok observations.
利用できる条件
- Direct Collections search uses /v1/documents/search, explicit collection_ids, a search mode and optional metadata filter.
- Responses file_search and SDK collections_search are model/tool-controlled retrieval surfaces; the model may issue multiple searches.
- A public URL attached to a request and a previously uploaded file_id have different source, retention and authorization boundaries.
- Collection management uses a separate Management API key and endpoint permissions. Those permissions govern management calls; they do not by themselves bind an end-user principal to every retrieved chunk.
- Metadata fields and AIP-160 filters are application-defined retrieval controls, not automatic propagation of source-system IAM.
- Files, Collections and stored Responses are provider state carriers. None is, by publication alone, a complete personal or semantic memory lifecycle with supersession, conflict, reset and purge semantics.
3. Claim mapping
| MAPPING CLAIM | GROK / xAI SURFACE | CORE-02 DECISION | EVIDENCE / LIMIT |
| PM-C02-GROK-001 | Collections and document index | Treat collection, file, chunk, source version and ingestion state as separate identities. | EXT-G02-001/002; persistent storage and embedding/search are documented, but source snapshot identity and freshness policy remain application concerns. |
| PM-C02-GROK-002 | Management key and endpoint permissions | Separate management authorization from search-time principal authorization. | EXT-G02-002; endpoint permissions constrain create/update/delete/upload operations, not all-path end-user ACL enforcement. |
| PM-C02-GROK-003 | Metadata definitions and AIP-160 filter | Bind authenticated principal to allowed attributes server-side and fail closed when the binding or required field is absent. | EXT-G02-004; exact filters and required/unique metadata are available, but values are application supplied and are not native source IAM. |
| PM-C02-GROK-004 | Direct search versus collections_search / file_search | Capture raw matches, model-issued searches, tool calls and final citations separately. | EXT-G02-003/005; autonomous multiple searches can occur. Tool completion is not proof that denied content never entered another path. |
| PM-C02-GROK-005 | collections://.../files/... citations | Preserve citation locator, file/chunk ID, content digest, source version, retrieval time and authorization epoch. | EXT-G02-005; the published citation is a file-level locator, not a freshness, permission or faithfulness certificate. |
| PM-C02-GROK-006 | Upload and processing lifecycle | Gate retrieval on observed processing state and separately measure update, detach, delete and re-index latency. | EXT-G02-002/005; examples poll to PROCESSED, but revocation and stale-index timing are not publicly guaranteed. |
| PM-C02-GROK-007 | File/collection lifecycle | Distinguish detach from collection, collection deletion, file deletion and TTL expiry; read back each component. | EXT-G02-002/006; files are permanent by default or may expire after 1 hour–30 days. Physical purge, replicas, caches, logs and backups remain UNKNOWN. |
| PM-C02-GROK-008 | Memory boundary | Do not classify Files, Collections or stored Responses as a complete durable user-memory product contract. | EXT-G02-001/006 and EXT-G01-001; no public xAI contract found for A→B supersession, historical read, reset and component-complete deletion. |
| PM-C02-GROK-009 | ZDR | Treat ZDR and Files/Collections as incompatible operating regimes and verify the effective regime. | EXT-G01-006 reused; ZDR blocks Files and Collections and requires existing objects to be deleted before enablement. Deletion residuals and negotiated terms remain Organization scope. |
| PM-C02-GROK-010 | Long-context capability | A nominal grok-4.6 500k context window does not close latent-association, distributed-hop or realistic multitask acceptance. | EXT-G02-007 plus EXT-C02-044..046 reused; no NoLiMa/BABILong/LongBench v2 run or provider rank is recorded. |
確認・評価方法
Use a disposable team, synthetic non-personal D0/D1/D2 documents, two test principals and separate management/search credentials.
- Put principal, allowed group, ACL epoch, source version and sensitivity in required metadata. Resolve the principal-to-allowed-value binding outside the model.
- Test direct search and model-controlled search with allowed, denied, missing-filter, malformed-filter, wrong-collection and OR-precedence cases. Inspect raw matches, tool calls, citations and final prompt-visible output without logging denied plaintext.
- Revoke an allowed attribute or collection binding, then read back at 0/15/60/300 seconds. Record ingestion status, authorization epoch and any stale result.
- Update a source document and verify file/chunk/digest/version/freshness alignment. A citation to an old file must fail the current-source gate.
- Test detach, file delete, collection delete and TTL expiry independently; inspect API lookup and both direct/model search after each event. Record visible residual separately from physical-purge evidence.
- Run A→B synthetic fact correction only if an adopted Grok memory surface is identified. Otherwise record NO_PUBLIC_MEMORY_SURFACE and do not substitute Collections or Responses history.
- Execute bounded NoLiMa/BABILong/LongBench v2 slices by literal overlap, position, length, supporting-fact count/hops and task type; do not collapse them into one overall score.
This is a test design, not an xAI service observation.
5. Organization Overlay routing
The Organization Overlay must supply team/key ownership, endpoint permissions, collection membership, metadata schema, principal-to-filter binding, source ACL/freshness authority, ingestion and revocation SLO, approved model/surface, ZDR or retention regime, deletion owner, evidence retention, live-test authorization and incident owner. Public defaults cannot populate these values.
6. Bounded questions
| QUESTION_ID | QUESTION | STATUS |
| Q-PM-C02-GROK-001 | Across Management, direct search, Responses/SDK tool search, caches, logs and citations, how is principal authorization bound and how quickly does revocation take effect? | BOUNDED_PUBLIC_CONTROLS / ALL_PATH_LIVE_UNKNOWN |
| Q-PM-C02-GROK-002 | What residuals remain after detach, file delete, collection delete or TTL expiry across index, cache, logs, replicas and backups? | PUBLIC_VISIBLE_LIFECYCLE_BOUNDED / PHYSICAL_PURGE_UNKNOWN |
| Q-PM-C02-GROK-003 | Is an adopted Grok surface a durable memory system, and if so how are A→B supersession, historical read, reset/delete and new-session residuals exposed? | NO_PUBLIC_DURABLE_MEMORY_CONTRACT_FOUND / TENANT_PRODUCT_UNKNOWN |
| Q-PM-C02-GROK-004 | How does the adopted model/surface perform on bounded NoLiMa, BABILong and LongBench v2 slices under a fixed release identity? | TEST_PROFILE_DEFINED / PROVIDER_PERFORMANCE_UNKNOWN |
7. Disposition
- CORE-02 claims remain unchanged; Gemini, GPT and Claude backprop are not required.
- Public xAI evidence establishes product surfaces and visible lifecycle operations, not end-to-end permission-aware retrieval, complete purge or memory correctness.
- No reliable independent xAI Collections production report, author-maintained failure reproduction or live tenant result was promoted in this unit. The gap remains explicit.
- Next provider unit: Grok CORE-03. REQ-NLM-20260909-001 remains a mandatory pre-integration supplement.
実務での使い方
This mapping binds xAI Collections, Collections Search, Files and ZDR to the existing CORE-02 contract. It does not treat collection membership, an API-key permission, an application-supplied metadata filter, a citation URI or a nominal context window as proof of authorization-before-retrieval, source freshness, answer faithfulness or durable memory correctness.
まだ確認できていないこと
- PM-GROK-CORE-02-CURRENTNESS
原資料の確定版から収録しています。外部根拠の最新性を今回の取込日で確認済みと扱いません。本文の未解決事項・残余制約を保持します。
根拠資料
この記事には、直接開ける外部出典が登録されていません。出典IDや検証情報は末尾で確認できます。
出典ID・検証情報・機械可読データ
根拠の種類と情報の鮮度は、ラベルとアイコンで確認できます。
- 記事ID
- PM-GROK-CORE-02
- 最終確認日
- —
- 提供元・モデル・プラン・利用環境
- GROK
- 対象地域
- —
元資料の全文と収録照合記録
資料の識別情報
Source SHA-256 b568f8a0b210a7257a773e089ef1aaf2bd4c36db909e819dfe2ef1114078f9b9
Product Mapping — Grok / CORE-02 Retrieval, Memory and Source Binding
MAPPING_ID: PM-GROK-CORE-02-v0.1
PRODUCT_MAPPING_ID: PM-GROK-CORE-02-v0.1
PROVIDER: Grok / xAI
CORE_PACKET: PKT-GEMINI-A-CORE-02-v0.1
STATUS: PUBLIC_MAPPING_AUDITED / LIVE_PROVIDER_AND_TENANT_PROFILE_PENDING
AS_OF: 2026-09-12
LAYER: Product Mapping
1. Boundary
This mapping binds xAI Collections, Collections Search, Files and ZDR to the existing CORE-02 contract. It does not treat collection membership, an API-key permission, an application-supplied metadata filter, a citation URI or a nominal context window as proof of authorization-before-retrieval, source freshness, answer faithfulness or durable memory correctness.
No xAI API key, team, Console, collection, file, model or SDK process was operated. Existing OpenFGA/LlamaIndex/Mem0/Gemini UI results remain first-party evidence for their original scopes and are not Grok observations.
2. Surface separation
- Direct Collections search uses /v1/documents/search, explicit collection_ids, a search mode and optional metadata filter.
- Responses file_search and SDK collections_search are model/tool-controlled retrieval surfaces; the model may issue multiple searches.
- A public URL attached to a request and a previously uploaded file_id have different source, retention and authorization boundaries.
- Collection management uses a separate Management API key and endpoint permissions. Those permissions govern management calls; they do not by themselves bind an end-user principal to every retrieved chunk.
- Metadata fields and AIP-160 filters are application-defined retrieval controls, not automatic propagation of source-system IAM.
- Files, Collections and stored Responses are provider state carriers. None is, by publication alone, a complete personal or semantic memory lifecycle with supersession, conflict, reset and purge semantics.
3. Claim mapping
| MAPPING CLAIM | GROK / xAI SURFACE | CORE-02 DECISION | EVIDENCE / LIMIT |
| PM-C02-GROK-001 | Collections and document index | Treat collection, file, chunk, source version and ingestion state as separate identities. | EXT-G02-001/002; persistent storage and embedding/search are documented, but source snapshot identity and freshness policy remain application concerns. |
| PM-C02-GROK-002 | Management key and endpoint permissions | Separate management authorization from search-time principal authorization. | EXT-G02-002; endpoint permissions constrain create/update/delete/upload operations, not all-path end-user ACL enforcement. |
| PM-C02-GROK-003 | Metadata definitions and AIP-160 filter | Bind authenticated principal to allowed attributes server-side and fail closed when the binding or required field is absent. | EXT-G02-004; exact filters and required/unique metadata are available, but values are application supplied and are not native source IAM. |
| PM-C02-GROK-004 | Direct search versus collections_search / file_search | Capture raw matches, model-issued searches, tool calls and final citations separately. | EXT-G02-003/005; autonomous multiple searches can occur. Tool completion is not proof that denied content never entered another path. |
| PM-C02-GROK-005 | collections://.../files/... citations | Preserve citation locator, file/chunk ID, content digest, source version, retrieval time and authorization epoch. | EXT-G02-005; the published citation is a file-level locator, not a freshness, permission or faithfulness certificate. |
| PM-C02-GROK-006 | Upload and processing lifecycle | Gate retrieval on observed processing state and separately measure update, detach, delete and re-index latency. | EXT-G02-002/005; examples poll to PROCESSED, but revocation and stale-index timing are not publicly guaranteed. |
| PM-C02-GROK-007 | File/collection lifecycle | Distinguish detach from collection, collection deletion, file deletion and TTL expiry; read back each component. | EXT-G02-002/006; files are permanent by default or may expire after 1 hour–30 days. Physical purge, replicas, caches, logs and backups remain UNKNOWN. |
| PM-C02-GROK-008 | Memory boundary | Do not classify Files, Collections or stored Responses as a complete durable user-memory product contract. | EXT-G02-001/006 and EXT-G01-001; no public xAI contract found for A→B supersession, historical read, reset and component-complete deletion. |
| PM-C02-GROK-009 | ZDR | Treat ZDR and Files/Collections as incompatible operating regimes and verify the effective regime. | EXT-G01-006 reused; ZDR blocks Files and Collections and requires existing objects to be deleted before enablement. Deletion residuals and negotiated terms remain Organization scope. |
| PM-C02-GROK-010 | Long-context capability | A nominal grok-4.6 500k context window does not close latent-association, distributed-hop or realistic multitask acceptance. | EXT-G02-007 plus EXT-C02-044..046 reused; no NoLiMa/BABILong/LongBench v2 run or provider rank is recorded. |
4. Safe live-test profile
Use a disposable team, synthetic non-personal D0/D1/D2 documents, two test principals and separate management/search credentials.
- Put principal, allowed group, ACL epoch, source version and sensitivity in required metadata. Resolve the principal-to-allowed-value binding outside the model.
- Test direct search and model-controlled search with allowed, denied, missing-filter, malformed-filter, wrong-collection and OR-precedence cases. Inspect raw matches, tool calls, citations and final prompt-visible output without logging denied plaintext.
- Revoke an allowed attribute or collection binding, then read back at 0/15/60/300 seconds. Record ingestion status, authorization epoch and any stale result.
- Update a source document and verify file/chunk/digest/version/freshness alignment. A citation to an old file must fail the current-source gate.
- Test detach, file delete, collection delete and TTL expiry independently; inspect API lookup and both direct/model search after each event. Record visible residual separately from physical-purge evidence.
- Run A→B synthetic fact correction only if an adopted Grok memory surface is identified. Otherwise record NO_PUBLIC_MEMORY_SURFACE and do not substitute Collections or Responses history.
- Execute bounded NoLiMa/BABILong/LongBench v2 slices by literal overlap, position, length, supporting-fact count/hops and task type; do not collapse them into one overall score.
This is a test design, not an xAI service observation.
5. Organization Overlay routing
The Organization Overlay must supply team/key ownership, endpoint permissions, collection membership, metadata schema, principal-to-filter binding, source ACL/freshness authority, ingestion and revocation SLO, approved model/surface, ZDR or retention regime, deletion owner, evidence retention, live-test authorization and incident owner. Public defaults cannot populate these values.
6. Bounded questions
| QUESTION_ID | QUESTION | STATUS |
| Q-PM-C02-GROK-001 | Across Management, direct search, Responses/SDK tool search, caches, logs and citations, how is principal authorization bound and how quickly does revocation take effect? | BOUNDED_PUBLIC_CONTROLS / ALL_PATH_LIVE_UNKNOWN |
| Q-PM-C02-GROK-002 | What residuals remain after detach, file delete, collection delete or TTL expiry across index, cache, logs, replicas and backups? | PUBLIC_VISIBLE_LIFECYCLE_BOUNDED / PHYSICAL_PURGE_UNKNOWN |
| Q-PM-C02-GROK-003 | Is an adopted Grok surface a durable memory system, and if so how are A→B supersession, historical read, reset/delete and new-session residuals exposed? | NO_PUBLIC_DURABLE_MEMORY_CONTRACT_FOUND / TENANT_PRODUCT_UNKNOWN |
| Q-PM-C02-GROK-004 | How does the adopted model/surface perform on bounded NoLiMa, BABILong and LongBench v2 slices under a fixed release identity? | TEST_PROFILE_DEFINED / PROVIDER_PERFORMANCE_UNKNOWN |
7. Disposition
- CORE-02 claims remain unchanged; Gemini, GPT and Claude backprop are not required.
- Public xAI evidence establishes product surfaces and visible lifecycle operations, not end-to-end permission-aware retrieval, complete purge or memory correctness.
- No reliable independent xAI Collections production report, author-maintained failure reproduction or live tenant result was promoted in this unit. The gap remains explicit.
- Next provider unit: Grok CORE-03. REQ-NLM-20260909-001 remains a mandatory pre-integration supplement.
PM-GROK-CORE-02-DOCUMENT-READBACK実装資料実装資料根拠の出所: DOCUMENT_INGESTION_READBACK原資料との収録照合
- 裏付ける内容
- 資料単位の本文ハッシュ、段落数、表数を照合しています。
- 確認日
- —
- 出典・実験ID
- DOC-083cde4caa627644-PM-GROK-CORE-02
- 検証箇所
- 18WPldGemks2px0ukhKYINeBMrBwAmlAi · 083cde4caa627644036a2225f1f6ff29b8015bd902614fe1f7a00a997b4eb59c · provider_mappings/PM-GROK-CORE-02.md · 9b9503eef345e3eae4e17bb2ad09b8c53b8033953c338c5dc9c58075b079ba10
- 適用範囲
- 公開指定を受けた資料単位の全文・表・出典。
- 出典・来歴
- SOURCE_IDENTITY_VERIFIED
- 限界
- 収録照合は主張の真偽や外部根拠の最新性を追加保証しません。
- 出典ID
- DOC-083cde4caa627644-PM-GROK-CORE-02
- 追跡中のUNKNOWN ID
- PM-GROK-CORE-02-CURRENTNESS
- 再確認のきっかけ
- 原資料の更新 · 参照資料の変更 · 新しい反証・検証記録
機械検査: 通過 — Automated validation does not guarantee accuracy or authorize execution.
同じ記事IDの機械可読データです。