array programming
Give an agent a durable, checkable way to recognise a array programming, record what state it is in, and decide what may be done with it.
Generated draft, first pass
This model was drafted by rule from what the registry knows about the thing. It proposes which bundles a real model will need and which questions research must answer. It is not researched and no sentence in it is sourced.
Generator: vr.draft.v3
Bundle → Layer → Finding → Questions Derived, awaiting review
6 bundles · 12 layers · 14 findings · 38 questions
Identity, naming and classification How an agent tells one array programming from another, and a array programming from things that resemble it.
Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.
Names and identifiers
The names this thing goes by and the identifiers that survive translation and time.
Preferred name, aliases and local names
Which name to use, which names mean the same thing, and which merely sound similar.
- What identifies and describes the name of a array programming, and in what units or vocabulary? definition
- Who or what asserted this about the name of a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once the name of a array programming is known, and what must it refuse? action
Stable identifiers and external keys
Identifiers that keep pointing at this kind of thing across systems and languages.
- What identifies and describes an identifier for a array programming, and in what units or vocabulary? definition
- Who or what asserted this about an identifier for a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once an identifier for a array programming is known, and what must it refuse? action
Classification and granularity
Where a array programming sits among kinds, and how finely a task needs to cut it.
Kind, parents and neighbouring kinds
The classes this thing belongs to and the ones it is next to.
- What identifies and describes the kind of a array programming, and in what units or vocabulary? definition
- Who or what asserted this about the kind of a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once the kind of a array programming is known, and what must it refuse? action
Distinguishing features
What separates a array programming from the things most often confused with it.
- What identifies and describes what distinguishes a array programming, and in what units or vocabulary? definition
- Who or what asserted this about what distinguishes a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once what distinguishes a array programming is known, and what must it refuse? action
State and lifecycle The states a array programming passes through and the events that move it between them.
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.
Lifecycle stages
From coming into existence to ceasing to be one of these.
Stages and transitions
The stages worth naming and what moves a array programming between them.
- What identifies and describes the lifecycle of a array programming, and in what units or vocabulary? definition
- Who or what asserted this about the lifecycle of a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once the lifecycle of a array programming is known, and what must it refuse? action
Observations and current status
What is observed about a array programming, how often and by whom.
Observation record
How an observation of a array programming is recorded so that it can be superseded rather than overwritten.
- What identifies and describes an observation of a array programming, and in what units or vocabulary? definition
- Who or what asserted this about an observation of a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once an observation of a array programming is known, and what must it refuse? action
Process, inputs and outcome How a array programming proceeds, what it needs and what it leaves behind.
An activity is known by its steps and its results, and both have to be recordable while it is still running.
Steps and sequence
The steps of a array programming, their order and what may run in parallel.
Steps, preconditions and completion
What has to be true before each step of a array programming and what marks it done.
- What identifies and describes a step of a array programming, and in what units or vocabulary? definition
- Who or what asserted this about a step of a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once a step of a array programming is known, and what must it refuse? action
Inputs, resources and results
What a array programming consumes and what it produces.
Inputs, outputs and side effects
The resources a array programming takes and the results it leaves, wanted or not.
- What identifies and describes the inputs and results of a array programming, and in what units or vocabulary? definition
- Who or what asserted this about the inputs and results of a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once the inputs and results of a array programming is known, and what must it refuse? action
Definitions and who holds them What array programming is taken to mean, and by whom.
When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.
Competing definitions
The main readings and the traditions behind them.
Definitions and their holders
Each definition with the school or body that holds it.
- Which definitions of array programming are in use, and which tradition or body holds each? definition
- What turns on the difference between them in practice? boundary
Operationalisation
How it is measured or applied when it has to be.
Measures and proxies
Instruments and indicators used to stand in for it.
- How is array programming operationalised or measured in practice, and by what instrument? measurement
- What does that operationalisation leave out, and when does that matter? boundary
Instances, use and consequence What counts as an instance of array programming and what follows from calling something that.
Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.
What counts as an instance
Clear cases, borderline cases and non-cases.
Tests for an instance
What would settle whether something falls under it.
- What would settle whether something is an instance of array programming? boundary
- Which borderline cases are argued about, and on what grounds? definition
Consequence of application
Rights, duties or decisions that follow from the label.
What the label licenses
What an agent may do once something is classified this way.
- What follows practically once something is treated as array programming? action
- What must an agent not infer from the label alone? action
Provenance, evidence and time Where every claim about a array programming came from and when it held.
A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.
Source and authority
Who said it, on what evidence, and how strongly.
Claim provenance and confidence
The authority behind each claim about a array programming and how confident it is.
- What identifies and describes a claim about a array programming, and in what units or vocabulary? definition
- Who or what asserted this about a claim about a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once a claim about a array programming is known, and what must it refuse? action
Time, versions and supersession
When a claim was true, when it was learnt, and what replaced it.
Validity period and supersession
How an old claim about a array programming is retired without being erased.
- What identifies and describes the validity of a claim about a array programming, and in what units or vocabulary? definition
- Who or what asserted this about the validity of a claim about a array programming, by which method, and when was it true? provenance
- What may an agent decide or do once the validity of a claim about a array programming is known, and what must it refuse? action
Classifiers Filled
- Family
- Thing Registry
- Category
- Activities and processes
- Entry kind
- abstract concept
- Plane
- ACT
- Domain
- ACT.ACT
What it is Derived, awaiting review
An activity registered under ACT.ACT. The registry names it; this draft has not been given a definition yet.
Why it exists Derived, awaiting review
Give an agent a durable, checkable way to recognise a array programming, record what state it is in, and decide what may be done with it.
Distinguishing features Derived, awaiting review
- Described in 17 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is.
What robots and AI may and may not do Derived, awaiting review
May
- observe it, measure it, record its state
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Missing, in the backlog
Not described yet. This gap is in the card backlog.
Links to other meta-models Missing, in the backlog
Not described yet. This gap is in the card backlog.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Direct properties not applicable Not applicable
- Made of: something that happens over time
- 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.
Recognition optional Derived, awaiting review
- Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about.
Capabilities and actions required Derived, awaiting review
- observed and measured
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Derived, awaiting review
- Described in 17 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is.
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Open questions
- 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 array programming, and on what evidence are they told apart?
- What may an agent decide or do once the name of a array programming is known, and what must it refuse?
- What may an agent decide or do once an identifier for a array programming is known, and what must it refuse?
- What may an agent decide or do once the kind of a array programming is known, and what must it refuse?
Machine files
Provenance
thing registry, generated draft (pass 1) · not researched
Built from: models/draft_model.php, wikidata
Generated by rule from registry facets. No source was read; every derived section awaits the research pass.