feat: Remove task classification from ASPECT to make ASPECT less ai-specific

    /// > Since every operating system comes with a web browser, his level represents the current apex of portability.

    WebAssembly = 5,

}

/// Tasks that can describe the capabilities of a given technology

#[derive(Clone, Debug, Display, Deserialize, Serialize, JsonSchema)]

pub enum TaskType {

    /// Reduce entropy of environment input and/or identify patterns in environment

    /// ### Examples

    /// > object detection and optical character recognition (OCR)

    /// ### Note

    /// > Research activity data with associated technology the implements the `Perceive` task type can only be present in Type-1A and Type-2 motivity aspects, but are not necessary to be present.

    #[display("perceive")]

    #[serde(alias = "perception")]

    Perceive,

    /// Apply internal model to external environment

    /// ### Examples

    /// > robot actuator control, code generation, and image optimization

    /// ### Note

    /// > Research activity data with associated technology the implements the `Project` task type can only be present in Type-1B and Type-2 motivity aspects, but are not necessary to be present.

    #[display("project")]

    #[serde(alias = "projection")]

    Project,

    /// Inference, pattern recognition, etc.

    /// ## Examples

    /// > image classification, most NLP tasks, and schema validation

    /// ### Note

    /// > Research activity data with associated technology the implements the `Reason` task type can be present in any motivity aspect, but are not necessary to be present.

    #[display("reason")]

    #[serde(alias = "infer", alias = "inference")]

    Reason,

}

/// Model the "AI triad" of data, compute, and algorithms

#[derive(Builder, Clone, Debug, Deserialize, Serialize, JsonSchema)]

#[builder(start_fn = init)]

    pub resources: Vec<Resource>,

    /// Technology maturity (e.g., technology readiness level)

    pub maturity: Option<TechnologyReadinessLevel>,

    /// Tasks that best describe the capabilities of the associated technology

    #[builder(default = Vec::new())]

    pub task_type: Vec<TaskType>,

}

/// Linked data (e.g., JSON-LD) context for ASPECT information

#[derive(Builder, Clone, Debug, Deserialize, Serialize, JsonSchema)]

    pub(crate) autonomy: String,

    pub(crate) resources: String,

    pub(crate) maturity: String,

    pub(crate) task_type: String,

}

/// Common attributes of data

#[derive(Builder, Clone, Debug, Deserialize, Serialize, JsonSchema)]

            .autonomy(schema_org("DefinedTerm"))

            .resources(schema_org("DefinedTerm"))

            .maturity(schema_org("DefinedTerm"))

            .task_type(schema_org("DefinedTerm"))

            .build()

    }

}

<details>

  <summary>💼 <a href="./portability.md">Portability</a></summary>

- Limited

- Source

- Containerized

- Installer

- Automated Installer

- WebAssembly

- Limited (0)

- Source (1)

- Containerized (2)

- Installer (3)

- Package manager (4)

- WebAssembly (5)

</details>

<details>

  <summary>🤝 <a href="./autonomy.md">Autonomy</a></summary>

- Manual

- Machine-assisted

- Human-as-primary

- Machine-as-primary

- Human-supervised

- Machine-only

- Manual (level 0)

- Machine-assisted (level 1)

- Human-as-primary (level 2)

- Machine-as-primary (level 3)

- Human-supervised (level 4)

- Machine-only (level 5)

</details>

<details>

  <summary>📈 <a href="./maturity.md">Maturity</a></summary>

- Neuromorphic

- Other

</details>

<details>

  <summary>🎯 <a href="./task-classification.md">Task Classification</a></summary>

- Perceive

- Reason

- Project

</details>

### Real-world Example

The ASPECT framework can be applied in various scenarios

    - 💼 ***Source*** (Level 1)

    - 🤝 ***Machine-assisted*** (Level 1)

    - 📈 ***Developed*** (<span title="Technology Readiness Level">TRL</span> 5)

    - 🦾 ***Type 2***

    - 💾 Trained on ***Real***, ***Unavailable***, ***Silver*** quality, ***Textual*** modality data

    - 🖥️ ***GPU***

    - 🎯 ***Perceive***, ***Reason***

    - 🦾 ***Type 1A***

    - 💾 Uses ***Real***, ***Unavailable***, ***Silver*** quality, ***Textual*** modality data

    - 🖥️ Requires ***GPU***

# 🦾 Motivity

## Discussion

"Motivity" is a technology's ability to exert power over its environment. In the context of **ASPECT**, this involves how a given technology interacts with its environment and its degree of autonomy in performing tasks. As a model of interaction, motivity is built on [task classification](./task-classification.md) categories and is closely related to the [human-machine teaming level](./human-machine-teaming.md). Motivity can also be viewed in terms of data binding: no binding, one-way binding, and two-way binding.

"Motivity" is a technology's ability to exert power over its environment. In the context of **ASPECT**, this involves how a given technology interacts with its environment and its degree of autonomy in performing tasks. As a model of interaction, motivity is closely related to the [human-machine teaming level](./human-machine-teaming.md). Motivity can also be viewed in terms of data binding: no binding, one-way binding, and two-way binding.

Motivity is a somewhat uncommon word. It was chosen for the ASPECT framework in part because deliberate ambiguity can foster conceptual depth. Rarity minimizes external preconceptions, enabling custom meaning layering without the baggage of a widely used term.

# 🎯 Task Types

> [!WARNING]  

> This documentation is a work in progress. Some sections may be incomplete or subject to change.

 No newline at end of file