{ "model": { "rank": 5717, "code": "thing-q178995", "model_id": "vr.tr.http-cookie", "name": "HTTP cookie", "purpose": "Enable an AI agent to recognise an HTTP cookie, assess its scope, lifecycle and exposure, and decide whether it may be accepted, sent, inspected, changed or removed.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q178995/", "tier": 2, "score": 65, "payload": { "layer": "wikidata", "aliases": [ "supercookie", "Cookies Having Independent Partitioned State", "third-party cookies", "zombie cookie" ], "aliasCount": 4, "merged": 4, "knownIn": 65, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q178995", "url": "https://www.wikidata.org/wiki/Q178995", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:06:15Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 12.6, "error": "Error: Internal error: {\n \"message\": \"API error (status 402 Payment Required): Grok Build usage balance exhausted\",\n \"http_status\": 402\n}", "retried": true }, "codex": { "seconds": 83.6, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07b1c-fdb9-7aa0-9b8d-7953e2b30d50\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: HTTP cookie\nRegistry id: vr.tr.http-cookie\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA" } } }, "metaModel": { "id": "THING-Q178995", "registryId": "vr.tr.http-cookie", "name": "HTTP cookie", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q178995/", "model": { "registry_id": "vr.tr.http-cookie", "name": "HTTP cookie", "purpose": "Enable an AI agent to recognise an HTTP cookie, assess its scope, lifecycle and exposure, and decide whether it may be accepted, sent, inspected, changed or removed.", "definition": "", "scope_statement": "This model owns an individual HTTP cookie as proposed, stored or transmitted by a user agent, including its observed attributes, storage context, request eligibility, purpose evidence and handling constraints.", "in_scope": [ "Cookie name, value handling and identity within a cookie store", "Creation through Set-Cookie or a supported client-side interface", "Domain, path, transport, same-site and partition constraints", "Expiration, replacement, eviction and deletion", "Script accessibility, transmission exposure and browser enforcement", "Evidence of purpose and authority to inspect or modify the cookie" ], "out_of_scope": [ "The authenticated session or account to which a cookie may refer", "The HTTP request, response or connection carrying cookie headers", "Local storage, session storage and other browser storage mechanisms", "The website's complete consent interface and policy", "Server-side token validation, authorisation and revocation systems", "The browser profile and its overall privacy configuration" ], "distinguishing_features": [ "It participates in the user agent's cookie mechanism: a cookie can be proposed through Set-Cookie or a supported client interface and selected for a Cookie request header.", "Unlike local storage, its eligible contents can be attached to HTTP requests automatically by the user agent.", "Unlike an arbitrary bearer token, its storage and dispatch are governed by cookie-specific scope and attribute rules; its value may nevertheless contain a bearer token.", "A Set-Cookie response header proposes a cookie but does not prove that the user agent accepted or retained it.", "A name-value pair observed in a Cookie request header does not expose the stored cookie's full attributes or uniquely identify its storage context." ], "characteristics": [ { "name": "Observation form", "kind": "category", "unit_or_values": "set-cookie proposal | stored cookie | request cookie pair | client-interface observation", "why_it_matters": "Determines which properties are directly observable and which require further evidence." }, { "name": "Cookie name", "kind": "category", "unit_or_values": "Exact observed name, including case and any prefix", "why_it_matters": "Supports identification and detection of naming conventions that may carry enforced restrictions." }, { "name": "Value handling class", "kind": "category", "unit_or_values": "unknown | non-sensitive | personal data | opaque identifier | potential credential", "why_it_matters": "Controls whether the value may be exposed, retained or compared without disclosing it." }, { "name": "Storage context", "kind": "relation", "unit_or_values": "User agent, profile or container, and observed partition key where applicable", "why_it_matters": "Separates cookies that appear identical but belong to different stores or partitions." }, { "name": "Host scope", "kind": "category", "unit_or_values": "Observed domain and host-only flag, or unknown", "why_it_matters": "Determines which request hosts may receive the cookie." }, { "name": "Path scope", "kind": "category", "unit_or_values": "Observed effective cookie path, or unknown", "why_it_matters": "Constrains request selection without establishing an isolation boundary against hostile scripts." }, { "name": "Access and dispatch attributes", "kind": "category", "unit_or_values": "Observed Secure, HttpOnly, SameSite and Partitioned settings, preserving absent and unknown states", "why_it_matters": "Supports assessment of transport, script access, cross-site dispatch and partitioning constraints." }, { "name": "Effective expiration", "kind": "measurement", "unit_or_values": "UTC timestamp when established; otherwise session-scoped or unknown", "why_it_matters": "Supports time-based eligibility checks while keeping browser session behaviour distinct from fixed expiration." }, { "name": "Storage lifecycle state", "kind": "state", "unit_or_values": "proposed | rejected | stored | replaced | expired | evicted | deleted | unknown", "why_it_matters": "Prevents a proposed or previously observed cookie from being treated as currently available." }, { "name": "Request eligibility", "kind": "state", "unit_or_values": "eligible | ineligible | indeterminate, relative to a specified request context", "why_it_matters": "Cookie dispatch depends on the request and user agent policy, not solely on the cookie." }, { "name": "Purpose evidence", "kind": "relation", "unit_or_values": "Links to application documentation, setter behaviour and observed consumers", "why_it_matters": "Distinguishes demonstrated function from guesses based on the cookie's name." } ], "affordances": [ "Inspect cookie metadata and compare values using an appropriately protected representation.", "Evaluate whether a cookie should be accepted or sent in a specified browser and request context.", "Set or replace a cookie through an authorised interface and verify the resulting stored state.", "Delete the intended cookie using its effective scope and storage context, then verify removal.", "Assess exposure and attribute changes against the application's intended behaviour.", "Trace setting and transmission events to investigate unexpected persistence or dispatch." ] }, "sources": [], "structure": { "bundles": [ { "id": "identity-and-observation", "name": "Identity and observation", "description": "Establish what was observed and which cookie instance that evidence identifies.", "rationale": "A header proposal, a stored cookie and a transmitted pair expose different evidence and must not be conflated.", "layers": [ { "id": "observation-evidence", "name": "Observation evidence", "description": "Locate the cookie observation within the HTTP or browser storage workflow.", "findings": [ { "id": "cookie-observation-form", "name": "Cookie observation form", "description": "Record whether evidence comes from a setter, the cookie store or an outgoing request, together with its time and context.", "questions": [ { "text": "Was this a Set-Cookie proposal, a stored cookie, a client-interface observation or a pair in a Cookie request header?", "kind": "definition", "id": "cookie-observation-form-q01" }, { "text": "Which response, script operation, storage inspection or outgoing request supplied the evidence, and when?", "kind": "provenance", "id": "cookie-observation-form-q02" } ] } ] }, { "id": "store-identity", "name": "Store identity", "description": "Resolve the cookie within a particular store without relying on its name alone.", "findings": [ { "id": "cookie-instance-resolution", "name": "Cookie instance resolution", "description": "Record the name, domain, path and relevant storage or partition context needed to distinguish candidates.", "questions": [ { "text": "Which name, domain, path, profile or container, and partition context identify the stored cookie?", "kind": "definition", "id": "cookie-instance-resolution-q01" }, { "text": "Could multiple stored cookies explain the observed request pair, and what evidence would distinguish them?", "kind": "boundary", "id": "cookie-instance-resolution-q02" } ] } ] } ] }, { "id": "request-scope-and-dispatch", "name": "Request scope and dispatch", "description": "Explain when the user agent may attach the cookie to a request.", "rationale": "The practical reach of a cookie depends on host, path, transport and contextual browser rules.", "layers": [ { "id": "destination-matching", "name": "Destination matching", "description": "Establish the effective destination scope rather than assuming it from the setter's URL.", "findings": [ { "id": "host-path-and-transport-match", "name": "Host, path and transport match", "description": "Record effective host-only or domain scope, path and Secure behaviour against a concrete destination.", "questions": [ { "text": "What effective domain, host-only status and path did the user agent store, including any defaults?", "kind": "measurement", "id": "host-path-and-transport-match-q01" }, { "text": "For the proposed request URL, which host, path or transport conditions allow or prevent selection?", "kind": "boundary", "id": "host-path-and-transport-match-q02" } ] } ] }, { "id": "contextual-dispatch", "name": "Contextual dispatch", "description": "Account for site relationships, partition context and user agent restrictions.", "findings": [ { "id": "same-site-and-partition-eligibility", "name": "Same-site and partition eligibility", "description": "Assess SameSite and partition behaviour using the actual navigation or fetch context and browser policy.", "questions": [ { "text": "What top-level site, initiating context, request method and navigation or fetch mode govern this dispatch decision?", "kind": "boundary", "id": "same-site-and-partition-eligibility-q01" }, { "text": "How do the effective SameSite setting, partition key, credentials mode and browser restrictions affect inclusion?", "kind": "measurement", "id": "same-site-and-partition-eligibility-q02" }, { "text": "Was the cookie actually attached to the request, and what evidence explains any difference from predicted eligibility?", "kind": "provenance", "id": "same-site-and-partition-eligibility-q03" } ] } ] } ] }, { "id": "acceptance-and-lifecycle", "name": "Acceptance and lifecycle", "description": "Track whether the cookie entered storage, remains there and can be removed.", "rationale": "Setting does not guarantee acceptance, expiration does not guarantee prior retention, and deletion must target the correct cookie.", "layers": [ { "id": "setting-and-replacement", "name": "Setting and replacement", "description": "Connect a setting attempt with its effective outcome.", "findings": [ { "id": "accepted-cookie-state", "name": "Accepted cookie state", "description": "Distinguish the attributes requested by a setter from the state accepted by the user agent.", "questions": [ { "text": "Which response or client operation attempted to set the cookie, and what attributes did it supply?", "kind": "provenance", "id": "accepted-cookie-state-q01" }, { "text": "Did the user agent reject, create or replace a cookie, and what stored-state evidence confirms the outcome?", "kind": "measurement", "id": "accepted-cookie-state-q02" } ] } ] }, { "id": "retention-and-removal", "name": "Retention and removal", "description": "Record effective lifetime and the evidence required to establish disappearance.", "findings": [ { "id": "effective-lifetime-and-deletion", "name": "Effective lifetime and deletion", "description": "Assess Max-Age, Expires, session retention and observed removal without equating browser deletion with server-side revocation.", "questions": [ { "text": "What effective expiration follows from the accepted Max-Age or Expires settings, or is retention session-scoped?", "kind": "measurement", "id": "effective-lifetime-and-deletion-q01" }, { "text": "Which authorised deletion operation targets this cookie's scope and storage context, and how will removal be verified?", "kind": "action", "id": "effective-lifetime-and-deletion-q02" }, { "text": "If the cookie disappeared or returned, is there evidence of expiration, eviction, explicit clearing, session restoration or a new setting event?", "kind": "provenance", "id": "effective-lifetime-and-deletion-q03" } ] } ] } ] }, { "id": "exposure-and-integrity", "name": "Exposure and integrity", "description": "Assess who can read, transmit or influence the cookie and how its value must be handled.", "rationale": "Cookies may carry credentials or identifiers, while their attributes provide specific protections with limited scope.", "layers": [ { "id": "value-exposure", "name": "Value exposure", "description": "Control access to the value according to its demonstrated or potential sensitivity.", "findings": [ { "id": "sensitive-value-handling", "name": "Sensitive value handling", "description": "Record the value's evidence-supported role and permitted representation in agent observations.", "questions": [ { "text": "What evidence shows whether the value is a preference, identifier, personal datum or credential, and what remains unknown?", "kind": "provenance", "id": "sensitive-value-handling-q01" }, { "text": "Can the task be completed using redaction, a protected comparison or metadata instead of exposing the raw value?", "kind": "action", "id": "sensitive-value-handling-q02" } ] } ] }, { "id": "attribute-protections", "name": "Attribute protections", "description": "Evaluate effective protections and remaining avenues of access or interference.", "findings": [ { "id": "read-and-write-boundaries", "name": "Read and write boundaries", "description": "Assess HttpOnly, Secure, SameSite and any enforced name-prefix rules without treating them as complete session security.", "questions": [ { "text": "Which script-access, transport and setting restrictions are demonstrably enforced for this cookie in the target user agent?", "kind": "measurement", "id": "read-and-write-boundaries-q01" }, { "text": "Could another permitted setter replace the cookie or introduce a same-name cookie with a different scope?", "kind": "boundary", "id": "read-and-write-boundaries-q02" }, { "text": "Which attribute changes would reduce the identified exposure while preserving required application behaviour?", "kind": "action", "id": "read-and-write-boundaries-q03" } ] } ] } ] }, { "id": "application-role-and-action", "name": "Application role and action", "description": "Connect the cookie's demonstrated function to permissible interventions and their consequences.", "rationale": "A technically possible cookie operation may disrupt application state or exceed the agent's authority.", "layers": [ { "id": "purpose-and-consumers", "name": "Purpose and consumers", "description": "Establish which application behaviour depends on the cookie.", "findings": [ { "id": "demonstrated-cookie-role", "name": "Demonstrated cookie role", "description": "Link the cookie to observed setters, consumers and functions while preserving uncertainty about opaque values.", "questions": [ { "text": "Which application component sets or consumes this cookie, and what evidence establishes its function?", "kind": "provenance", "id": "demonstrated-cookie-role-q01" }, { "text": "Does the cookie hold application state directly or reference state owned by a session, account or other neighbouring model?", "kind": "boundary", "id": "demonstrated-cookie-role-q02" } ] } ] }, { "id": "permitted-interventions", "name": "Permitted interventions", "description": "Determine whether a proposed operation is authorised and whether its intended effect occurred.", "findings": [ { "id": "cookie-operation-authority-and-effect", "name": "Cookie operation authority and effect", "description": "Record task authority, relevant user choices and expected consequences of accepting, modifying or deleting the cookie.", "questions": [ { "text": "What task authority and applicable user choices permit the proposed inspection, setting, transmission or deletion?", "kind": "action", "id": "cookie-operation-authority-and-effect-q01" }, { "text": "What application effect is expected, and what observation will confirm it without assuming that cookie deletion revokes server-side state?", "kind": "action", "id": "cookie-operation-authority-and-effect-q02" } ] } ] } ] } ] }, "openQuestions": [ "Which browser families, versions and embedded clients must the model cover, and how do their defaults, prefix enforcement and third-party cookie policies differ?", "Which partition identifiers and storage-key details are observable through the intended inspection interfaces?", "How do the target user agents apply lifetime caps, eviction and session restoration, and which outcomes can be distinguished from available evidence?", "What application-specific evidence establishes this cookie's purpose, sensitivity and dependency on server-side state?", "Which applicable policies and recorded user choices constrain this cookie's use, and where is the authoritative evidence maintained?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 23 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "discipline or field of knowledge", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a HTTP cookie, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise an HTTP cookie, assess its scope, lifecycle and exposure, and decide whether it may be accepted, sent, inspected, changed or removed.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: supercookie, Cookies Having Independent Partitioned State, third-party cookies, zombie cookie.", "4 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 65 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a HTTP cookie, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "read it and act on what it says" ], "howItIsRecognised": [], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "supercookie", "Cookies Having Independent Partitioned State", "third-party cookies", "zombie cookie" ] } ], "standing": "Described in 65 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 4 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one HTTP cookie from another, and a HTTP cookie from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a HTTP cookie sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a HTTP cookie from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a HTTP cookie passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a HTTP cookie between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a HTTP cookie, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a HTTP cookie is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a HTTP cookie says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a HTTP cookie contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a HTTP cookie and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "subject-and-method", "name": "Subject matter and method", "description": "What HTTP cookie studies and how it establishes anything.", "rationale": "A field is identified by its questions and its methods, and those are what distinguish it from the fields next to it.", "layers": [ { "id": "subject", "name": "Subject matter", "description": "The questions it takes as its own.", "findings": [ { "id": "subject-record", "name": "Questions and objects of study", "description": "What it is about, stated so a neighbouring field can be told apart.", "questions": [ { "id": "subject-record-q01", "text": "What questions and objects does HTTP cookie take as its own?", "kind": "definition" }, { "id": "subject-record-q02", "text": "Which questions does it share with a neighbouring field, and who claims them?", "kind": "boundary" } ] } ] }, { "id": "method", "name": "Method and evidence", "description": "How claims are established and what counts as evidence.", "findings": [ { "id": "method-record", "name": "Methods and standards of evidence", "description": "The methods used and what they are taken to establish.", "questions": [ { "id": "method-record-q01", "text": "By what methods does HTTP cookie establish claims, and what counts as sufficient evidence?", "kind": "provenance" }, { "id": "method-record-q02", "text": "What kind of claim can this field not settle, and where should an agent look instead?", "kind": "action" } ] } ] } ] }, { "id": "institutions-and-classification", "name": "Institutions and classification", "description": "Where HTTP cookie is practised and how catalogues place it.", "rationale": "The institutional footprint is the evidence that a field exists as a field rather than as a topic.", "layers": [ { "id": "institutions", "name": "Institutional markers", "description": "Societies, journals, degrees and departments.", "findings": [ { "id": "institution-record", "name": "Bodies and venues", "description": "Where the field organises itself.", "questions": [ { "id": "institution-record-q01", "text": "Which societies, journals or degrees mark HTTP cookie as an established field?", "kind": "provenance" }, { "id": "institution-record-q02", "text": "What would show that it is emerging or dissolving rather than established?", "kind": "boundary" } ] } ] }, { "id": "classification", "name": "Classification schemes", "description": "Where library and research classifications put it.", "findings": [ { "id": "classification-record", "name": "Codes and their disagreements", "description": "The classification codes that place it, and where they differ.", "questions": [ { "id": "classification-record-q01", "text": "Which classification schemes place HTTP cookie, under what codes?", "kind": "definition" }, { "id": "classification-record-q02", "text": "Where do those schemes disagree about its scope?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a HTTP cookie came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a HTTP cookie and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a HTTP cookie is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a HTTP cookie, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a HTTP cookie, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a HTTP cookie is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }