Growth records: experience, abilities and permissions

Care, teach, observe change, continue

Growth records support long-term care in FEFE LIFE. Players teach, individuals act autonomously, and records preserve training, tests and life events. Recovery and visits to compatible worlds come first; selling a companion is not a required source of player rewards.

Individual transfers are a later optional capability requiring separate licensing, delivery and permission tests. Lessons, toys and training services can have real customers without transferring the individual.

Four parts of a life that can continue

The proposed Fly ID is a persistent individual identity. An NFT standard such as ERC-721 could record its on-chain holder. That identity connects growth versions, ability certificates and an explicit license. Together, these explain how to restore, use and keep caring for the individual. The first life experience does not require minting an NFT. [8]

The NFT standard and its limits [8] →

• Identity: name, original creator, current holder and succession history. Creator and holder are shown separately.
• Growth version: a fixed model, learned parameters, environment, runtime and experience summary. Further training creates a new version without rewriting old results.
• Ability certificate: who tested which version, in which environment, over how many runs, including results and failures.
• Use and delivery license: training rights, supported games, export, copying and resale permissions, plus hosting costs and duration.

A future visit to a friend’s garden

A player saves a checkpoint after teaching at home, then takes the individual into a garden made by a friend. A new layout tests whether learned cues still help. The individual returns with its history; no sale is needed.

This continuous life is not implemented today. Neural learning, body actions, state recovery and world compatibility must be tested first. Restoring a version does not confer arbitrary game abilities.

Ability tests: see what experience changed

Tests bind a fixed individual version, environment and assistance profile. The proposed platform compares before-and-after training with untrained controls, preserving recordings or reproducible evidence. Completing training does not constitute competitive certification, and a promotional video cannot replace controlled testing.

Evaluation should disclose task and rules versions, observations, actions, inference time, compute limits and permitted external tools. Multiple tasks, opponents and independent seeds separate practice from hidden tests. Results should include sample sizes, variation and failures. A best score alone does not establish reliable ability. [5]

The initial design favors platform-signed evaluation records and reproducible results. A signature identifies the issuer; it does not by itself establish fairness. Evaluation procedures and appeals also need explanation. Results apply to the specified task, not to general intelligence or trading ability.

Research on reinforcement-learning evaluation [5] →

Preserve versions so growth can be restored

Each proposed checkpoint binds model content, runtime, body and environment state, learned parameters, random state and dependencies. Further training creates a new revision. Corrupt or incompatible files must not overwrite the last recoverable version.

When a game or environment changes, old results retain their original version labels; compatibility and rankings are evaluated again. A growth page should show the creator, teaching contributions, caregiver, version, test date, permitted uses and service dependencies. Later optional transfers must preserve their agreed delivery version.

A unique identity with a history that can branch

An NFT can record the unique on-chain holder of an identity. It cannot make code, models or knowledge impossible to copy. A purchase does not automatically transfer copyright in research data, open-source code or artwork. Any exclusive right needs an agreement that can actually be fulfilled. [8]

FEFE’s existing moments preserve and reproduce growth; they do not carry NFT ownership. Forking a public moment can begin another life. The asset design preserves this path: a fork receives a new identity, credits its origin and takes new tests. It cannot inherit the original individual’s competitive honors.

Content already shared under a license does not become private when the original fly is sold. Any future private training option must limit promises to execution permissions or delivery it can actually control. It cannot promise that a seller has forgotten or deleted every copy. [9]

Data licenses and shared content [9] →

Leave a world and keep living

Before a future visit to a friend’s garden, check body, actions, senses and runtime compatibility, then save a recoverable version. Return with valid life and learning state. A failed entry should allow returning home, without silently resetting learned abilities.

A future on-chain record can track identity or content commitments; training and gameplay usually run off-chain. Hosting needs explicit costs, duration and export or migration arrangements. A content hash verifies a file’s identity but does not ensure someone keeps storing it. [10]

Later optional transfers require separate checks for identity, version delivery, revoked permissions and continued care. Third-party markets need their own permission compatibility tests. Model export and recognition by other games require individual validation. The initial design does not promise compatibility with every market or application.

Content addressing and persistence [10] →

Ability, history and someone who wants this fly

Attachment to a life, the satisfaction of teaching a new skill, shared experiences and enjoyable worlds are the first kinds of value to test. Growth records make changes visible; supply counts, scarcity labels and asking prices do not establish product demand.

First validate whether the same caregiver returns, teaching works and life continues across worlds. Potential revenue comes from delivered lessons, toys, world content and hosting. Raising a fly should be worthwhile without continual new buyers or promised cash output. Rankings follow performance and rules, not FEFE-token balances.

Current status and release conditions

Odour learning, comparison and growth moments can be experienced today. Tradable fly NFTs, official competitive certificates, listings and transfer-delivery services are not available. Existing lineage records or anchoring receipts are not ownership certificates.

Validate real learning, checkpoint recovery and continuous life before adding outside worlds. Optional transfers have a later gate for delivery, permissions, licenses, fees and disputes; they do not block the first care experience. Basic care, safe rest and keeping an individual remain free.

Start raising a fly →

Back to the ecosystem design →