AU2022228135A1 - DaoCanRock – methods, systems and devices exploiting advanced digital technologies where accountability and governance in collaborative environments is important either to participants, communities or sovereignties including peer-to-peer organizations and where there may be resourcing or safety risks. - Google Patents

Abstract

DaoCon & DaoRock - methods, systems and devices exploiting advanced digital technologies where accountability and governance in collaborative environments is important either to participants, communities or sovereignties including peer-to-peer organizations and where there may be resourcing or safety risks.

Description

DaoCon

AUSTRALIA

Patents Act 1990

Description

REFERENCE TO RELATED APPLICATIONS

Intellex: separate provisional patent IP#2021900208

SafeXShare:separate standard patent IP#2021900281 DigikeyP : separate provisional patent #2021901862

FunjMakBrake : separate provisional patent #2021901953

MkTrck : separate provisional patent #2021902872 ParkCare: separate provisional patent #2021902928

TickerTag separate provisional patent #2021902946 PredEPrev separate standard patent#2021218217

SpecQBook : separate provisional patent #2021902885 FlowMake : separate standard patent IP#2021286396

HoHoBal: separate provisional patent IP#2021903942 GlobMake: separate provisional patent IP#2021904017

MkMkT: separate provisional patent IP#2021904151

H4Z:separate standard patent IP#2021261831 SourceMonitor : separate provisional patent IP#2021900208

SauceMonitor :separate innovations patent IP#2021104349 TickTrackPLUS :separate standard patent IP#2021232845

TranspairPLUS :separate standard patent IP#2021236587 SafeEShare : separate innovations patent#2020100425

DiagML : separate innovations patent#2020901672 PCMF : separate innovations patent#2020902071

IncentiHealth : separate innovations patent#2021103255

TickTraceE : separate provisional patent IP#2021901140 BAC : separate provisional patent#2020902146, innovations patent#2021103348 DetPat : separate standard/divisional patent IP#2021202215 (prioritized by IP#2018100540)

FIELD OF THE INVENTION

Embodiments of the present invention are in fields of Commerce, Research, Health, Consumer Digital

Infrastructure, Industry, Safety, Ecology, Mining and Human Rights on account of:

• the value of being able to responsibly produce, develop, accrue and use resources via more direct

andformalized collaborations and specifically including larger sets of data relating to wider

ranges of activities with more stakeholders including the general public and the need to obtain

and manage those resources and associated data with accountability more easily and for highest

value, including where implementation involves significant systemsfunded by andfor the benefit

of the public,

• a significant needfor accountability andfacilitation of safe grass roots participation in more

flexible patterns of cooperation (including activity resourcing, authority, personal accreditations,

decision-making etc),

• the opportunities in digital technologies such as block chain to manage transactions more

immediately according to systemised and auditable agreements (including contracts extending

on direct permission models of security) created over economic and digital assets for managing

nuanced control more flexibly and quickly,

* the likelihood and attractivenessfor more efficient administration wherever resources and data

can be used safely and acceptably with respect to equitability and privacy.

It is likely to particularly suit collaborative environments in situations where significant levels of

resourcing or safety risks require accountability which is very important either to participants,

communities or to sovereignties.

BACKGROUND OF THE INVENTION

Economic efficiency increasingly justifies higher levels of computerization for managing processes, labour and natural resources used to produce goods and services. There is also new value being realized

from authenticity, reduced risk and stronger accountability along the way to higher quality outcomes. Cooperation and reference to previous experience via data and machine learning plays a significant role

in attaining and improving these outcomes for continually increasing economic efficiency and

productivity. New digital technologies applied strategically and realistically promise more reliable

cooperation with data easier to collect and cheaper to store. If new techniques and infrastructure allow

data collection while still protecting basic rights like privacy, their standardization and commoditization

will go on to ensure consumers can confidently participate in the digital revolution safely. With this

much deeper and wider use, the digital revolution will be more powerful. This will maximize the

associated productivity gains and allow more tightly efficient levels of cooperation at "product level"

including product-stapled offsets within significant carbon emissions control efforts as well as learge

industry mentoring of communities to recover economies ravaged by COVID.

A fully scalable, international technical standards based framework that includes a robust but workable

and flexibly applicable governance framework will make the cooperation required to maintain our

healthy planet and peoples as safe and comfortable as possible.

BRIEF SUMMARY OF THE INVENTION

The present invention relates to systems, methods and devices for implementing an essential set of

coordinated governance interactions between independent parties who work as independent interests

but still want to manage cooperate, collaboration or input as a member of some defined group most

likely peer-to-peer organised with any required controls being via one of a variety of styles of

governance that could be imposed with only agreed, flexible and transparent accountability by all

relevant parties / individuals including when these individuals are transacting within homes, public

spaces &/or workplaces.

The embodiment of such collaboration will be referred to generically in this specification as

Decentralised Autonomous Organisations (DAOs). The letters "Dao" in the DaoCon name of the

invention superficially refers to a particular governance style that is convenient and natural in

collaboration but potentially quite challenging to regulators and the ideals of accountability due to the

potential poorly defined ties of membership between peer-managed members, as implied minimally

allowable by its description as a Decentralised Autonomous Organisation.

With certain controls in place a DAO becomes a Cooperative. Controls applied in cooperatives operating under the various Cooperatives Laws in Australia and elsewhere can be very effective but also

potentially overly onerous for some collaborations. Control modifications or application of different

levels of rigour by constituting or not under different bodies of law (eg Corporations, CATSI,

Associations) can produce governance regimens more appropriate to different applications or even sub

applications (ie a department within a larger organisation) that need more or less accountability focus in

certain areas over others. It also includes accountability management in collaborations that are not

embodied according to laws but controlled by contracts (eg uJVs) including where in different ways it

implies cooperation with government or governments. The controls included in DaoCon have flexibility

sufficient to allow DaoCon to be used in any of these situations encouraging assurance by sovereign

governments (specifically through their Court system) to balance a necessary level of oversight.

In this way it is a realistic and efficient option for accountable collaboration across borders eg A regional

cooperative-like collaboration run with DaoCon' accountabilities and producing product-stapled carbon

reduction activities for sale as part of the carbon-heavy product rather than necessitating customers to

purchase potentially more expensive and dispersed benefit traded offsets. Participation in side markets by members of the DaoCon can be included in DaoCon contracts (benefitting all collaborators) or where

this has not been contracted, quite separately where surplus efforts could be slotted into other carbon

and biodiversity offset revenue streams (eg ACCU, Biodiversity). See Australian Provisional Patent

IP#2021261831 ("H4Z").

The DaoCon invention includes a separate permanent device ("DaoRock") allowing ongoing population

of data models as historic evidence as well as authentications specific to essential accountability

controls on collaborative activities whether collaborators are from the same organization or not, or use

the same systems. It is envisioned that mandatory use of the permanent device should be a function of

the relevant legislation, possibly allowing for a lag in the designed designs availability. In any case, the

data model's flexibility can be applied on hard or soft resources and KPs (eg safety) allowing flexible,

secured data collection and protection as evidence of accountability for processes and/or assets.

The processes and assets may include : physical controls, detections, accesses to bodies of information,

shared data models and or environments (sovereign, personal, professional, cloud based) and anything

where advanced digital technologies are found useful in pursuit of credible accountability.

Such technologies include block chain and a range of identification protocols as required for the variety

of combinations possible and transactions involving DAO member owned device/s used (including

mobile phones, wearable and portable devices and also jurisdiction-specified identification devices

where these are to be applied).

With the potential for fast application of block chain controls comes a need to ensure accountability

sufficient for the potential for safety risk. Despite what seems to be a chicken and egg scenario we know

both chickens and eggs do exist so it is not inappropriate to plan to use DaoCon devices to implement

better block chain management systems where technologically imposed protections (including positively

1Dao in various intonations of Chinese can mean "arrive", reach", "go to or leave for", "turn upside down", "be finished, ready", "pour a cup of tea" and is often indicative of an included opposite effect. This is not inappropriate to the range of often self-benefitting objectives driving one's collaboration with others.

identifying technicians as well as their use of safety protocols driven by robustly applied software

techniques when implementing and making changes on equipment controlled by distributed devices)

will help ensure flexibility is less likely to compromise worker, equipment, product or environmental

safety.

That is, it is envisaged that appropriately trained and qualified software technicians, potentially working

for different employers will eventually be able to use DaoCon devices to reinstall software within

systems protected by appropriate other devices (eg as discussed in Australian Innovations Patent

IP#202103348 BlackBoxAuthorityCoordinator ("BAC")) even should other governance be relied upon to

reinforce or cover known exposures or gaps in control when reprogramming block chain controlled

devices.

Similarly it is envisaged that appropriately trained and qualified data technicians, potentially working for

different employers will eventually be able to use DaoCon devices to record only responsible use of

appropriately qualified, unbiased and sufficiently credentialled items of data for machine learning.

Once the component techniques and technologies are implemented and the risk of cyber mischief minimized:

• blockchain-implemented identifications will be able to reliably confirm identities 'live';

• experience will confirm the effectiveness of yet-to-be standardised techniques such as "Detpat",

possibly enhanced with Al processing for automatically recording implemented controls, data

protection, sharing and transferring collected data as evidence (See Australian Standard

patent#2021202215 ("Detpat") and Australian Provisional Patent IP#2021901862 ("DigiKeyP"));

and * the DaoRock will reliably record accountability with such data, able to be presented as evidence

when required.

To be successfully implemented as a governance standard the required DaoCon framework necessarily

also requires :

• Laws upholding the standards of governance sought by this system including simple definitions

and rules defining mandatory reporting of accountabilities of interest to parties at risk,

government and/or regulators;

• Good will and cross jurisdictional confidence in equitable business cases sufficient to justify

mass-production of wide ranges of devices conforming to interoperable standards of

architecture and function that transparently and sufficiently address globally common needs

including : data sovereignty, human safety, data security and data privacy.

• Development of standards and regulatory consistency of architecture components enabling best

commoditization, including for implementations with gradations in standards of personal

identity, authority and privacy and where non-personal 'personal technology' devices may also

prove easily and safely used for remote permanently installed system components or as product

or service trackers (including animals) until standard devices specific to the purpose are

generally available;

• Education, audit and independent assessments or research efforts that produce version

controlled proforma models, including DaoCon configured accountabilities and DaoSchemes

potentially with increased efficiency and operational flexibility - but that explicitly highlight to

all potential adopters the governance tradeoffs (weaknesses) and matching dependencies

thought relevant to the particular model / model grouping;

• Use of standardised global or standardisable time and position reference systems; and

• Commitment by member users to implement designs that support transparency of

accountability and priority for addressing the needs of vulnerable impacted populations

including explicitly sought mitigation/s where existing schemes of reward and risk apportionment allow potentially suboptimal outcomes including shared accountabilities,

unnecessarily longfinancial settlement delays, unnecessary transaction charges and system

delays (which all increase the risk of instability).

In this specification :

• The regimen being proposed is called a DaoCon (DAO control system) for managing governance

within a DAO that exists in at least one named home jurisdiction;

• There is assumed to be existence of or preference to create a standard set of jurisdiction

identifiers as envisioned and agreed on by peer jurisdictions in pursuit of common national

interest benefits (including anti kleptocratic crime, anti money laundering etc); • There is assumed to be existence of or preference to create a standard essential set of minimum

items for positively identifying an individual within a jurisdiction (eg <Jid><lid>) and a standard workaround where there may be a lack of technological capability (eg

<JidlidlookupListlD><lookup list position>);

• There is assumed to be an architectural scheme in common and legal use that allows one

coordinating device to arbitrate controls of devices within a single system that allows devices

operated by more than one DaoCon to have a level of control input (eg a truck loading device

with controls from the production warehouse door control panel and a truck driver from

another company issued with an appropriate "key device". See Australian Innovations Patent

IP#202103348 BlackBoxAuthorityCoordinator ("BAC") and Australian Provisional Patent

IP#2021901862 ("DigiKeyP"));

SA DaoCon regimen is classified as a "<home jurisdiction> Order <N> DaoCon" where at any

particular time :

o <home> denotes the home jurisdiction eg "Australian" in which the governance is

regulated; and

o <N> is the minimum number defined for the DaoCon of DaoExec members required to

vote infavour to execute a decision (ie normally the number that represents the majority of a legal vote of DaoExec members) of the DaoCon (ie Default is 1, with that

executive defaulted to be the initial device owner who, if this accountability were not

personally acceptable, would necessarily arrange to remove themselves and/or

nominate a different individual as owner of the DaoCon);

• Each DaoCon will have a designated DaoExec, being a single or set of N (N=1, 2,3...) or more

people, each as a jurisdiction-identified individual (ie pairings of <lid>, <Jid>); and • A single jurisdiction-identified individual who becomes a legal member of a DaoCon at a

standardized point in time (whether or not also separately nominated as one of/the only

member of the DaoExec), is called a DaoCom (Dao Commissioner) of the DaoCon. This is

preserved permanently for the DaoCon including after the role is relinquished (with global

standard timestamping); • Any proposition asserting an accountability or delegation of responsibility for any of the

accountabilities of a DaoCon by the DaoCon or one of its DaoComs is called a DaoScheme; • Any other proposition is just called a proposition even when processed with accountabilities

managed through a DaoCon;

• The single special device devised for managing the continuous legitimacy, accountability, and

stored history of the DaoCon and its DaoSchemes and potentially other transactions and

decisions of the members of the organization is called a DaoRock; while • The copy of the DaoRock data maintainable by regulators in the relevant jurisdiction is called the

DaoKlock (a Known Accountability-lock); and

• Subsets of the DaoKlock may be made accessible by the home jurisdiction to other jurisdictions

as a DaolKlock (a "Dao-Eye-Klock" as in Internationally Known Accountability-lock), according to

specifications made by international agreements between governments in the home jurisdiction and other jurisdictions.

The DaoRock device design is for delivery with installed interoperable organisation configuration

software capable of managing essential DaoCon transactions and permanent storage of the DaoCon

commands and decisions representing the wide variety of coordinated interactions of DaoCom

members transacting through services populating the data model related to the essential accountability

of the organization and its members being set up with the DaoCon and DaoRock.

As required by as-yet-to-be-formulated laws within each jurisdiction, various functions of the DaoCon

will always require consistency between the DaoCon and its DaoRock. Inconsistencies between them

assessed by comparison of completion to a trial DaoRock of any outstanding updates against the current

DaoCon will generate an alert protocol, including alert to specified regulators where this has been

regulated as part of a base implementation. This would be most sensibly different for different types of implementations including where Associations operate under Associations legislation as distinct from

Corporations Legislation or a technical maintenance group operates under Work Safety Legislation.

Each DaoRock device is initially owned and authorized by a human individual who may own and legally

execute using assigned devices for each DaoCon as long as each DaoCon has a separate DaoRock device.

By going on to use the DaoCon, as the DaoRock owner the individual remains asserted on the DaoCon as

a DaoExec member of the DAO. Such a person may go on to add other executives or relinquish that

ownership/executorship &/or DaoCom membership, but in line with the accountability aims of the

system and the device, will be for evermore recorded as the initial owner, executor and member of the

DaoRock device being used to manage the DAO.

Even if the DaoCon ceases to exist as a DAO agent-requiring-governance within the current home

jurisdiction, the DaoRock (and likely the regulator copies of the DaoKlock and DaolKlock) will continue to

provide evidence of its historic existence in that jurisdiction for any point in time occurring between

pairs of upper and lower date-times (internationally standardized time timestamps). Regulated remnant assets that were managed with the DaoCon or use similar identification within other systems (such as

discussed in Australian Provisional Patent IP#2021901862 "DigiKeyP" or Australian Provisional Patent IP#2021902872 "MkTrck") would remain marked to the zombie DaoCon in the old jurisdiction if block

chains and transaction junctures are regulated with sufficient quality and security. Providing

international agreements enable it, it will remain possible for the old jurisdiction to raise liabilities to the

newly domiciled entity for incurred transfer taxes if the assets are later able to be identified in another

jurisdiction.

Access to Other Data

Member-configurable data items on the devices can be used remotely to variously enable access,

transfers and control of other devices and systems with or without dialogues. This is a two edge sword

of course so may not be enabled for many DaoCons but does allow synchronizing, triggering, processing,

auditing, measuring, and recording of data for regulatory reporting or for use as evidence with

accountability to a particular point in time being recorded for sharing across the Dao and even

potentially permanently recorded as a member-configurable data item on the recipient DaoRock device

and - where required and configured properly on the DaoCon - with immediate access for regulators.

Decision-making and data sharing transactions can be enacted peer-to-peer simply with individual

contribution accountability, with accountability recorded as a delegation or voted motion or, where

relationships are more complex (eg across Co-operatives or governed by contract) accountably

authorized and or coordinated by one or more DaoComs as individuals working for different

organizations but collaborating via the particular DaoCon. This potentially includes managing a system

composed of a device or set of devices. A system supervisory device as discussed in Australian

Innovations Patent #202103348 ("BlackBoxAuthorityCoordinator BAC") can be programmed to allow

updates by a different organization from a different DaoCon if Australian Standard patent#2021202215 ("Detpat") is applied to set up coordination of updates made from the supervisory device to one or

more remote device/s owned by members of a different DaoCom (who presumably would record their permission for this to be done via their acceptance of it within some explicit appropriate supervisory governance described within a position description provision or their vote on a motion allowing it).

In all cases these functions are configured using meta-sharing tools operating on control schemes accessed with controls imposed by one or more different enabled DaoCons imposing various grades of

identification in combination with access security set up in the system being accessed and if required

due to perceived unaddressed operational or cyber risks being recorded as a report stored on a

DaoRock.

Advanced digital technologies including block chain design techniques (See Australian Standard

patent#2021202215 ("Detpat")) are used to implement simple data protection, sharing and transfer

contracts as well as the advanced governance functions and links updating member coordinated

processes involving distributed data platforms, shared information assets, contracts including

employment infrastructure (using award structures and KPIs as well as payments as per provisional

patent#2021900732 ("PartTime") ) and other data-focused functions in accordance with mutual

agreements for data privacy (See Australian Innovations patent#2020100425 ("SafeEShare"), Australian

Provisional IP#2021900281 ("SafeXShare")) and according to law.

Indirectness and Flexibility v Accountability :

It is expressly recommended that jurisdictions implementing a DaoCon system, regulate to explicitly not

allow DaoCons themselves to be allocated as members of another DaoCon. While such compounded

indirection is theoretically manageable, it increases complexity, risks obscurity and therefore reduces

the incentive of responsible parties to pay real attention to their accountability. It is more robust to

nominate a lead individual of a "subordinate" DaoCon (N=1) as a member of a "higher" DaoCon in order

to represent an hierarchy of accountability. If careful and it is also acceptable to the decision-makers of

the higher organization, several individuals of the "subordinate" DaoCon (N>1) could become members

of the upper DaoCon, with due regard to the quality of the DaoScheme that allowed it. It is possible that

the situation might suggest the two organizational units should explore becoming the same DaoCon.

Ideally a DaoScheme would be able to systemise the kinds of essential accountability flows and gaps

identified by a good analyst examining position descriptions for objectives related to a group of function types per individual eg "Production", "Sales", "Fin", "Safety", "IT", "Research", limitations in scope, base budget catering for long term cost commitments such as operations staff and asset charges, discretionary budget, KPIs names, KPI units and goal rates. At is simplest this might consist of the latest pdf copy of DaoCom's position Description.

Where ambitious gap analysis is required position descriptions could be summarized or otherwise

arranged according to techniques outlined in Australian Standard patent#2021202215 ("Detpat") and

recorded as a DaoSchemes approved by the DaoExec and explicitly delegated as part of the DaoCon's

accountability model to DaoComs with appropriate experience, a sufficient level of resources and

checkpoints in line with these to accomplish it.

Where an organization has a high degree of contract/employee accountability, DaoCons member

configurable data items would reference data in members' individual "PartTime" devices as defined by

provisional patent#2021900732 ("PartTime") to populate DaoCon accountability qualifications related to

education and experience through "PartTime" configuring dialogues. Otherwise DaoCon member

configurable data items would collect (presumably for authentication separately if deemed necessary)

via its own DaoCon member data collection sub-dialogues.

Besides mapping the fixed accountabilities of staff via their text-only or DaoScheme'd position

descriptions, the possibility of implementing other DaoSchemes presents infinite opportunities for

flexibility where individuals with sufficient skill may be enabled and choose to enable control schemes of

lesser quality including those ordinarily called "workarounds".

In some cases the hazard or risk in play in a situation will never justify systemization of a workaround. In

some cases the effort mitigating controls to the nth degree is disproportionate (in terms of reward and

risk) to the outcome. In any case though, the DaoScheme remains as evidence that an election to

systemize alternative control schemes in some formalized innovative or collaborative way (of the many

possible variations on the spectrum of possibilities that would likely sit between the extremes possible)

has been made by an executing or delegating single member or by the set of voting executive or

members.

In some instances governance with more complex decisionmaking will require systemization of more

complex voting schemes, and some even involving multiple DaoCons. As an example, a co-operative

would likely require votes within membership types to determine a sub-groups vote to the whole

cooperative, possibly involving votes for sub-organisation acceptable relative priorities. This can still be accomplished atomically where a special voting scheme authorized by each sub-organisation (or if

particularly tightly managed, the N=1 DaoExec DaoCom of each sub-organisation) implements multi

component vote dialogues using programmed KPIs to process determined an average, or identified max

or min relative weightings of one sub-group relative to their own membership type for subsequent

combination with raw votes and normalizations as described in lapsed Australian Innovations Patent

IP#2018100428 invented by this same inventor. The outlined data model allows this and other more

complex variations.

It is also envisioned that there would be standard sets of DaoScheme proformas made available

managing essential accountability capability parameters such as banking details, insurance details etc.

Authority Identification and Accountability Context :

Because the soft and hard architecture of components of the DaoCon are designed to allow maximum

flexibility, transactions are managed at the 'lowest' (smallest, most independent, cheapest) level

possible, beginning with one natural person being always designated the initial device owner even if the

device is not yet used. Thus the DaoRock device production process will designate the initial owner who

will need to be removed as a member if they are not willing to accept any accountability for later

transactions of the DaoCon. This implies a need for incorporation of an acceptable identification-at

point-of-sale transaction and/or other regulator supervised transactions and protocols sufficient to the

quality of the objectives of the DaoCon system.

Identification data stored would include the identification data items required by the jurisdiction.

Obviously there would be efficiencies and mutual regulatory reward (more easily reduced money

laundering) where this is standardized across jurisdictions.

Besides the implied structures implementing the identification of the N or more members of the

DaoExecs at a particular point in time, further accountability is managed through the DaoScheme structures, imposed via "Detpat" design principles (Australian Standard IP#2021202215). The "Detpat" structure is inherent to the DaoCon and DaiRock device's implementation. Further DaoScheme implemented accountabilities overlay the total decision-making scheme already existing at a relevant decision-making time, including any DaoComs qualifying for and being subscribed to the classifications designated to be taking accountability for an asset, process or decision (ie those associated according to the existing rules for a particular decision made by or delegated from a particular decision-making group) and thus forms a total accountability through overlays at recorded times on models of accountability that already applied at that time in the context of the individually attributed decision making of the DaoCon group related to the individual proposition at that time.

As such, it is part of the invention that DaoSchemes are able to be inspected by all members who are

designated to be executives within the DaoCon as well as regulators or who are involved in the

delegation or scheme either directly or otherwise. Wider reporting could be configured as imposed by

regulators so that other required devices/systems can access the data conveyed by the messages

produced by the DaoRock or other DaoCon components.

Coordination with other devices for authorizations and other functions

In any envisioned embodiment, the present invention in a 5G environment and possibly also within

satellite communication systems can be set up to coordinate with other devices and systems to assist a

person to securely configure, store or grant access to information related to themselves or their

enterprises, including on portable DigiKeyP devices for the purpose of data logging and control. Using

meta-sharing commands within programs they are then able to provide controlled information easily,

conveniently and with some measure of confidence to other parties requiring to transact information

related to the DAO. This may include any of the following patents : Australian provisional patent

#2021900208 ("IntellEx"), #2020903375 ("TickTrack"), #2020903487 ("TickStack"), #2020904085

("Authstack"), #20204630 ("Transpair"), #2021901140 ("TickTraceE"), #2021901302 ("OptiKeyP"),

#202103348 ("BlackBoxAuthorityCoordinator BAC") and #2021901862 ("DigiKeyP").

This could include confirmation ofidentification of the device wearer (or other party via their worn device) when at close proximity to an external identifying device (as determined within a jurisdiction to be an approved ID station via facial, voice or other bio recognition), with an interrogation sequence nominally including steps similar to the following:

1. WEARER: Press button = Identity Confirmation,

2. DEVICE : Sends a shortrange (<im) message to the IDstation,

3. IDstation :Nothing (= "Not close enough") OR performs facial scan OR says "Tell me your Name"

4. WEARER :Looks at camera or "John Smith",

5. IDstation :Your device carries the same ID I have for the image/voice/ bioscan I am seeing/hearing

you as now. While you continue wearing your device uninterrupted it will remain primed to conduct

authorised transactions in your name.";

The DaoCon device (DaoRock) being in most circumstances a necessarily small device, but where high

levels of authentication are justified requiring the operation of cameras or microphones, will sometimes be implemented to have a camera onboard or to only operate for high risk functions in co-location with

biorecognition devices operating cross-network identification protocols.

Lesser variations of this authentication and authorization process can be offered by member with whom

the device owner is attempting to collaborate or to transact data but it becomes a responsibility of the

device owner to accept the risks of doing so.

The DaoCon architecture requires significant upfront investment but once investments are made by

governments as well as private concerns, it will very flexibly enable better accountability even by small

poorly resourced efforts as well as by more significant and possibly much higher value collaborations

more confidentially encouraged across teams, businesses, sectors, regions and nations, both

economically (through implemented payment contracts) and logistically (data driven controls including

supply chains) using techniques such as those discussed in Australian Standard Patent#2021202215

("DETPAT"), Australian Innovations Patent IP#202103348 BlackBoxAuthorityCoordinator ("BAC") and Australian Provisional PatentIP#2021901862 ("DigiKeyP").

Data model Components

A DaoCon will eventually include tools configuring use of proforma data items corresponding or related

to:

• Home Jurisdiction

• Order (ie N, default 1)

• Date and Time DAO created (when sold, a global standard)

• Date Last DAO updated (a global standard)

• DaoRocklD (used with jurisdiction-defined authentication process)

• DaoKlocklD (used by regulators in the jurisdiction)

• DaolKlocklD (used by other jurisdictions for authentication in their jurisdictions)

• DAO Identification details (list / superset as required by regulators of each type using it) o Dao Type

o RegType

o Id used by home regulator

o Name

o Address

o etc

• List of N DaoExecs (first initially populated at time of creation, others added by) o Jid

o lid (used with jurisdiction-defined identification process to authenticate operations)

o Dateln (a global standard)

o DateOut (a global standard)

o Qualifications statement (likely also a structure for purpose of checking legitimacy

o Name, Address, qualification summary for reporting purposes only to base

authentication level

o etc

• List of DaoComs (members)

o Jid

o lid (used with jurisdiction-defined identification process to authenticate operations)

o Dateln (a global standard)

o DateOut (a global standard)

o Qualifications statement (likely also a structure for purpose of checking legitimacy o Name, Address, qualification summary sufficient for reporting purposes to base authentication level o etc

• List of DaoSchemes (Multiple entries, related to accountability changes only, format depends on

type/extent of implementation)

o Date and time Authorized (a global standard)

o Date no longer used

o Date and time Schedule (a List of milestone events and timings, global time standard)

o Each either Simple/Authentication / Self-Configured/ Complex ie: • Either Simple eg

• PDF SOR Authentication (DaoCom configured) eg

• Authentication Level Name

• Command Sequence Dialogue Listing/s - Case by case programs

communicating with other systems. • OR Self-Configured Collaboration (DaoCom configured) eg

• Motion- Text like a project instruction

• Director (provides budget possibly via a complex delegation as below)

• Voting Structure - as determined by vote type and vote processing, it

may involve more than one field per DaoCom participant and

potentially even links into fields set up in the DaoCom's membership

contract 2

• Vote Type Name

• Vote Processing

• Vote Time Limit

• Other parameters as useful for managing reporting and or collaboration

process SOR Complex Systemised Delegation (more than one dimensions per person

likely) eg

2 More complex voting schemes with nominated weightings for members of OTHER "co-op" membership types to be used in averaging, or identifying max or min weightings as described in lapsed Australian Innovations Patent IP#2018100428 invented by this same inventor.

• Delegation Name

• Types

• Scope limitation 1

• Scope limitation 2

• Scope limitation N

• Base budget (zeros where necessary to avoid doubleups)

• Discretionary budget (zeros where necessary to avoid doubleups)

• KPIs name (used to populate link to update DaoCon-reportable KPs)

• KPI unit

• KPI goal rate

o Authority by Listed DaoCom/s (member/s)

Each either Simple delegation /Self-Configured ie:

• Either Simple eg the relevant DaoCom

o Jid

o lid (whatever is delivered by jurisdiction-defined identification

process to authenticate operations)

o Name, Address, qualification summary sufficient for reporting

purposes

o etc • OR Complex Systemised Vote approved by at least N sets of:

o Jid

o lid (whatever is delivered by jurisdiction-defined identification

process to authenticate operations)

o Name, Address, qualification summary sufficient for reporting

purposes o Etc

o Current Status ie : • Either Simple eg "Complete", "No longer used" OR

• OR Complex (a list of links into reportable KPIs, possibly outside of the DaoCon)

• List of Authentication Levels eg Base, I (for international), 1, 2, 3 named and thereafter

referenced as DaoScheme

• List of DAO Contracts eg membership contracts if they apply (Multiple, format depends on

type/extent of implementation including links to KPI models) - similar to DaoScheme

• List of Reportable Propositions eg Gap analysis (Multiple, format depends on type/extent of

implementation) - entries similar to DaoScheme but with addition where appropriate of:

o Vote Name

o Vote Type Name

o Vote Put Time

o Vote Result

o Vote Complete timestamp

• List of Reportable Outcomes eg risk assessments, investigations, digitally protected images

recorded as evidence

• List of Reportable KPIs

o Type

o KPI-id (link optionally used by DaoSchemes) o Description

o Command

o LatestCopy date and time (global time standard)

o Processed Copy

o Process Description

o Process Structure (weightings, period boundaries, offsets etc) • List of Reportable events eg meeting datetimes, meeting objectives, agendas, minutes,

attendances, trades

• List of Reportable Accountability-related Correspondences IN (eg membership conditions)

• List of Reportable Accountability-related Correspondences OUT (eg membership alerts,

negotiations, use of DaoRock) • List of Management Reports (Multiple, format depends on type/extent of implementation) eg

Gap analysis -similar to DaoScheme but each with added

o Regularity definition

o Circulation list as one or more of: • Jid • lid (whatever is delivered by jurisdiction-defined identification process to

authenticate operations)

• Name, Address, qualification summary sufficient for reporting purposes

• Etc

• DaoAudit Trail - corresponds to DaoRocklD or other device in its absence.

• Dao Auditor Identification

o Jid

o lid (whatever is delivered by jurisdiction-defined identification process to authenticate

operations)

o Name, Address, qualification summary sufficient for reporting purposes

o etc

• Dao Audit Assessment details - datestamped audit report opinion

• Other Audit details

• DaoRegulator - single point of contact with the relevant regulator:

o Jid

o lid (whatever is delivered by jurisdiction-defined identification process to authenticate

operations)

o Name, Address, qualification summary sufficient for reporting purposes

o etc.

The DaoCon/DaoRock will maintain its own logs as a list of changes including

• Date and time Authorized (a global standard)

• Command Text

• Issued by (authority)

• Identified to level

Extended Model enabling Commercial Leverage of DaoScheme Authorities as Licence:

The basic data model assumes cost of membership is managed within DaoCom configured DaoSchemes.

However, for decreasing latency in software licensing and also therefore posAl

sibly increasing momentum for efforts to add "formwiring" of infrastructure accountabilities into

DaoCons, a commercially informed accountability allocation framework that could cement onseller

relationships and increase the quality of accountability gap analysis. It also implies techniques discussed

in Australian Standard Patent#2021202215 ("DETPAT").

A DaoScheme for Licence management within a DaoCon (loadable as a contract message):

• Type eg Full Free, Free when Identified, Free with limit, Cost with limit

• Currency

• RateType (One off, per day, week, month, year...)

• Cost

• DateTimeLast(a global standard)

• Service Storage Area :

o DateTimeStart(a global standard)

o ServicelD

o LicencelD

o Bank Account Details o History details

DaoCon Functions :

The following is a not exhaustive list of functions that would be made available to configuration stubbs

used by the relevant DaoCom to invite members and program the DaoCon/DaoRock using multidevice

messaging protocols to users running the relevant apps across networks including 5G/oT using the

DaoConApp.

Commands would be recorded into only accretive DaoCon/DaoRock logs in line with the credibility

objectives.

GetDaoLock.RocklD DaoRock provides its unique RocklD and DaoCon Name

whether or not it has already been allocated to a DaoCon SetDaoLock.Name <Name> _(Re) Names the Dao

SetDaoLock.Rock <RocklD> Attaches the DaoRock to the DaoLock

SetDaoLock N sets N eg 3 for a typical supervisory board, 1for a

normal reporting department, 1for centralized control

LetDaoAuthenticate <L> <Name> <Uname> Checks identity of user to level L

JoinDaoCon <Name> Messages a sufficiently authenticated user's interest to

join the named DaoCon as a join message with the users

name (or similar)

AddDaoCon <Name> <Uname> Messages a sufficiently authenticated user's interest to

join the named DaoCon either through the app directly

or via a link in an email message. Also education

package.

AddDaoCom <DaoName> <MemberAddress>_Sends a member the member details input dialogue for

their access via the downloadable app

RemoveDaoCom <DaoName> <Uname> Disengages a DaoCom member.

AddDaoExec <DaoName> <Uname> Sends a DaoCom member the details input dialogue for

their accession as an executive of the DaoCon via the

downloadable app. Also education package.

RemoveDaoExec <DaoName> <Uname> Disengages a DaoExec but keeps them as a DaoCom

member

AddDaoScheme <DaoName> <SchemeName>_Input dialogue to configure a named DaoScheme. This

would include authentication AddDaoxxxxxx <DaoName> <xxxxxxName> Input dialogue to configure a named Daoxxxxxx where

xxxxxx corresponds to an appropriately shortened

version and parameter list for any of :

• DaoKlocklD (used by regulators in the jurisdiction

only) • DaolKlocklD (input by DaoCom. Used by other

jurisdictions for authentication to information as

agreed by one government to government in other

jurisdictions) • DAO Identification details (list / superset as

required by regulators of each type using it) • DaoExecs (first initially populated at time of

creation, others added from population of

completed DaoCom registrations) :

• DAO Contracts eg membership contracts if they

apply

• Reportable Propositions

• Reportable Outcome

• Reportable KPI

• Reportable events eg meeting datetimes, meeting

objectives, agendas, minutes, attendances, trades

• Reportable Accountability-related Correspondences

IN (eg membership conditions)

• Reportable Accountability-related Correspondences

OUT (eg membership alerts, negotiations, use of

DaoRock)

• Reportable Management Reports

• DaoAudit Trail - corresponds to DaoRocklD or other

device in its absence.

• Dao Auditor Identification

• Dao Audit Assessment details - datestamped audit

report opinion

• Other Audit details

• DaoRegulator - single point of contact with the

relevant regulator : • Identifification level - one of the named

DaoSchemes of Type Authentication

BackUpDaoCon <DaoName> (Used especially where a DaoRock is not being used)

Synchronise <DaoName> Check DaoRock is accessible and consistent

Ping <DaoName> Check DaoRock is accessible

ReportDaoCon <DaoName> Alerts regulator if there is an unsettleable inconsistency

between the DaoCon and the DaoRock.

PublishDaoField <DaoName> <Daoxxxxxx> Allows public access as designated by the item type.

ShareDaoField <DaoName> <DaoField> Allows collaborative "cloud style" input on one of the

collaboration-allowable fields as designated by the field

type and records changes with identification (<Jid>,<id>) and timestamps. Useful for composing motions within

DaoSchemes ready for taking a vote.

PutDaoConScheme <DaoName> <DaoScheme>_Seeks vote or input according to vote type and

DaoScheme set up for it (with any LetDaoAuthenticate

<L> <Name> <Uname> identification checks if this has

been included as part of the named voting Scheme) and

records results ready for the vote completion trigger

which can be set up as part of the voting protocol at

which time a vote timestamp is applied to the decision.

Embodiments in devices with different capabilities for different contexts :

In one embodiment, the present invention includes DaoCons constituted as governance systems

represented by a DaoRock device for :

• a single-sovereignty identified DAO organization [ie Organizations and individuals identified

within a single jurisdiction, both identifications of which would be for ones already identified in

the jurisdiction or not yet existing in the jurisdiction or * a common cross-sovereignty DAO identification [international or Multi-Jurisdictionally Identified

Organisation and Individuals, both identifications of which require combination with an

identifier for the home jurisdiction within which the organization or person already exists or

wishes to be identified in) for uniqueness in that jurisdiction.

In any embodiment, the present invention in a 5G environment and possibly satellite communications

would also likely include functions assisting sovereign border protection and where agreed and

implemented by the parties concerned, links and KPI reporting of enterprise supply chain and other

types of management with systemizations useful to accountability tracking including semaphore

functionality (as per Australian Standard Patent#2021202215 "DETPAT") and with items of information

obtained across networks and carried on the device having been made explicitly accessibly through

specifically suited data management techniques (eg Australian Standard Patent#2021202215 "DETPAT")

for presentation to normal graphics and other devices.

In various embodiment then, a system is described, including a memory that stores computer

executable components; a hardware processor, operably coupled to the memory, and that executes the computer-executable components stored in the memory, wherein the computer-executable components may include a components communicatively coupled with the processor that execute the aforementioned steps.

In another embodiment, the present invention is a non-transitory, computer-readable storage medium

storing executable instructions, which when executed by a processor, causes the processor to perform a

process for generating measurements, the instructions causing the processor to perform the

aforementioned steps.

In another embodiment, the present invention is variously a system for taking measures including

images or identifications using various different technologies, the system in each case comprising the

base device having such functionality (eg 2D camera, microphone, electromagnetic reader, sampler), a

processor, a display, a first memory; a server comprising a second memory and a data repository; a

telecommunications-link between said user device and said server; and a plurality of computer codes

embodied on said first and second memory of said user-device and said server, said plurality of

computer codes which when executed causes said server and said user-device to execute a process

comprising the aforementioned steps.

In yet another embodiment, the present invention is a computerized server comprising at least one

processor, memory, and a plurality of computer codes embodied on said memory, said plurality of

computer codes which when executed causes said processor to execute a process comprising the

aforementioned steps.

Other aspects and embodiments of the present invention include the methods, processes, and

algorithms comprising the steps described herein, and also include the processes and modes of

operation of the systems and servers described herein.

Yet other aspects and embodiments of the present invention will become apparent from the detailed

description of the invention when read in conjunction with the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS DETAILED DESCRIPTION OF THE INVENTION

Overview

With reference to the figures provided, embodiments of the present invention not sufficiently covered

in the brief summary of the invention are now described in detail.

In the following description, for purposes of explanation, numerous specific details are set forth in order

to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the

art that the invention can be practiced without these specific details. In other instances, structures,

devices, activities, and methods are shown using schematics, use cases, and/or flow diagrams in order to

avoid obscuring the invention. Although the following description contains many specifics for the

purposes of illustration, anyone skilled in the art will appreciate that many variations and/or alterations

to suggested details are within the scope of the present invention. Similarly, although many of the

features of the present invention are described in terms of each other, or in conjunction with each

other, one skilled in the art will appreciate that many of these features can be provided independently

of other features. Accordingly, this description of the invention is set forth without any loss of generality to, and without imposing limitations upon, the invention.

Data Model Embodiments

Embodiments of the present invention include a data model appropriate to the data items and functions

described in the brief summary.

Accordingly, other embodiments of the present invention include a computer system, comprising a

memory that stores computer-executable components; a processor, operably coupled to the memory,

and that executes the computer-executable components stored in the memory, wherein the computer

executable components comprise a data collection component communicatively coupled with the

processor that receives user parameters from the user or a user device and receives at least one input

from the user device, the at least one record including suitable data items including data input by the user and where required confirmed identification made by other devices able to communicate with the

device running the dialogue; a data extraction component communicatively coupled with the processor that extracts and redeposits data as directed by the users commands or actions or data embedded into messages received by the user's device, and that performs parsing on the user's device to extract further items of information from the device or other accessible devices according to permissions on the user's device and the other device from which data is being extracted; and a data analysis component that performs data detection based on standard measures and generates the required response as a message using the device program and the messaged record it previously received.

Hardware, Software, and Cloud Implementation of the PresentInvention

As discussed, the data (e.g., photos, textual descriptions, and the like) described throughout the

disclosure can include data that is stored on a database stored or hosted on a cloud computing platform.

It is to be understood that although this disclosure includes a detailed description on cloud computing,

below, implementation of the teachings recited herein are not limited to a cloud computing

environment. Rather, embodiments of the present invention are capable of being implemented in

conjunction with any other type of computing environment now known or later developed.

Cloud computing can refer to a model of service delivery for enabling convenient, on-demand network

access to a shared pool of configurable computing resources (e.g., networks, network bandwidth,

servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly

provisioned and released with minimal management effort or interaction with a provider of the service.

This cloud model can include at least five characteristics, at least three service models, and at least four

deployment models.

Characteristics may include one or more of the following.

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as

server time and network storage, as needed automatically without requiring human interaction with the

service's provider.

Broad network access: capabilities are available over a network and accessed through standard

mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones,

laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a

multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned

according to demand. There is a sense of location independence in that the consumer generally has no

control or knowledge over the exact location of the provided resources but can be able to specify

location at a higher level of abstraction (e.g., country, state, ordatacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to

quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for

provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a

metering capability at some level of abstraction appropriate to the type of service (e.g., storage,

processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.

In another embodiment, Service Models may include the one or more of the following.

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's

applications running on a cloud infrastructure. The applications are accessible from various client

devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer

does not manage or control the underlying cloud infrastructure including network, servers, operating

systems, storage, or even individual application capabilities, with the possible exception of limited user

specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud

infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (laaS): the capability provided to the consumer is to provision processing,

storage, networks, and other fundamental computing resources where the consumer is able to deploy

and run arbitrary software, which can include operating systems and applications. The consumer does

not manage or control the underlying cloud infrastructure but has control over operating systems,

storage, deployed applications, and possibly limited control of select networking components (e.g., host

firewalls).

Deployment Models may include one or more of the following.

Private cloud: the cloud infrastructure is operated solely for an organization. It can be managed by the

organization or a third party and can exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific

community that has shared concerns (e.g., mission, security requirements, policy, and compliance

considerations). It can be managed by the organizations or a third party and can exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group

and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or

public) that remain unique entities but are bound together by standardized or proprietary technology

that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

A cloud computing environment is service oriented with a focus on statelessness, low coupling,

modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure that

includes a network of interconnected nodes.

The cloud computing environment may include one or more cloud computing nodes with which local

computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone, desktop computer, laptop computer, and/or automobile computer system can communicate. Nodes can communicate with one another. They can be group physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices are intended to be exemplary only and that computing nodes and cloud computing environment can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

The present invention may be implemented using server-based hardware and software.

For interface with a user, the hardware may include one or more user input devices (e.g., a keyboard, a

mouse, a scanner, a microphone, a web camera, etc.) and a display (e.g., a Liquid Crystal Display (LCD)

panel). For additional storage, the hardware my also include one or more mass storage devices, e.g., a

floppy or other removable disk drive, a hard disk drive, a Direct Access Storage Device (DASD), an optical

drive (e.g. a Compact Disk (CD) drive, a Digital Versatile Disk (DVD) drive, etc.) and/or a tape drive, among others. Furthermore, the hardware may include an interface one or more external SQL

databases, as well as one or more networks (e.g., a local area network (LAN), a wide area network

(WAN), a wireless network, and/or the Internet among others) to permit the communication of

information with other computers coupled to the networks. It should be appreciated that the hardware

typically includes suitable analog and/or digital interfaces that communicate with each other.

The hardware operates under the control of an operating system, and executes various computer

software applications, components, programs, codes, libraries, objects, modules, etc. indicated

collectively by reference numerals to perform the methods, processes, and techniques described above.

The present invention may be implemented in a client server environment.

In some embodiments of the present invention, the entire system can be implemented and offered to the end-users and operators over the Internet, in a so-called cloud implementation. No local installation

of software or hardware would be needed, and the end-users and operators would be allowed access to the systems of the present invention directly over the Internet, using either a web browser or similar software on a client, which client could be a desktop, laptop, mobile device, and so on. This eliminates any need for custom software installation on the client side and increases the flexibility of delivery of the service (software-as-a-service), and increases user satisfaction and ease of use. Various business models, revenue models, and delivery mechanisms for the present invention are envisioned, and are all to be considered within the scope of the present invention.

In general, the method executed to implement the embodiments of the invention, may be implemented

as part of an operating system or a specific application, component, program, object, module or

sequence of instructions referred to as "computer program(s)" or "computer code(s)."

The computer programs typically comprise one or more instructions set at various times in various

memory and storage devices in a computer, and that, when read and executed by one or more

processors in a computer, cause the computer to perform operations necessary to execute elements

involving the various aspects of the invention. Moreover, while the invention has been described in the

context of fully functioning computers and computer systems, those skilled in the art will appreciate

that the various embodiments of the invention are capable of being distributed as a program product in

a variety of forms, and that the invention applies equally regardless of the particular type of machine or

computer-readable media used to actually effect the distribution. Examples of computer-readable

media include but are not limited to recordable type media such as volatile and non-volatile memory

devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only

Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), and digital and analog communication media.

Claims (3)

Claims

1. Claims of basic DaoCon method

a. Implement a generalisable technological solution using advanced digital technologies

for more robust governance of distributed autonomous organizations and other types of

organization;

b. Use digital software mechanisms operating on a variety of different devices accessible

via networks and employing advanced digital technologies to implement accountability

control schemes variously able to enable different grades of governance including:

i. essential governance processes,

ii. additional process and asset governance and governance tool hierarchies

configured by authorized users,

iii. data flows able to be configured by data input by authorized users' structures

via meta-sharing configuration tools schemes including with those hierarchies

designed using the techniques described in Australian Standard

patent#2022203235 ("Detpat Div"), as well as

iv. structures for determining and implementing and recording various

identifications and accountabilities fitting into the above, and

v. an architecture that can include permanent digital records via a DaoRock device

where preferred;

c. Implement and test schemes of governance control using other devices using Detpat

techniques appropriate to key functions and bodies of law;

d. Apply the architecture with advanced digital technologies where this is implemented

including via block chain techniques.

2. Claims of one or more non-essential method variations or additions to the claims of the DaoCon

method of claim 1 include :

a. Propose to hardware suppliers for a joint DaoCon - DaoRock OS development project including a messaging system able to apply block chain techniques as per Australian

Standard patent#2022203235 ("Detpat Div");

b. Propose a joint DaoCon - DaoRock OS development project with other jurisdictions;

c. Implement the Model enabling Commercial Leverage of DaoScheme Authorities as

Licencing schema and management tools.

3. The DaoRock Device of claim 1 comprising:

a. one or more memories; and

b. one or more processors, communicatively coupled to the one or more memories, to:

i. receive a communication that is an app to configure the device to use or share

information from as part of a system or subsystem,

ii. receive information identifying one or more self-support actions performed by

the authorized user in relation to the data model being shared for the DaoCon

and recorded permanently within the DaoRock device,

iii. assign the communication to a position in a support queue based on when the

communication is received, wherein the support queue includes:

1. information identifying positions of other communications received

from other users,

2. information identifying when the other communications are received,

& 3. information identifying self-support actions performed by the other

users,

iv. associate the information identifying the one or more self-support actions

performed by the user with information identifying the position of the

communication in the support queue,

v. apply respective weights to the one or more self-support actions performed by

the user,

vi. generate a score for the communication based on applying the respective

weights to the one or more self-support actions performed by the user,

vii. modify the position of the communication in the support queue based on the

score, and

viii. perform one or more actions based on modifying the position of the

communication in the support queue and or as required for the operation of the

DaoRock according to settings and configurations of the DaoCon and DaoRock.

Application Number #X by Julianne Cripps Clark (was Provisional 2022900007) 07 Sep 2022

Statement of Proposed Changes

2. Please delete the current claims file (if it exists, having most likely been composed by you from pages 32-34 in my full-specification-with-claims original submission 3 January 2022) and replace it with pages 32-34 (Claims 1-3) from the file here attached. Markup copy also attached. 2022228135

Thank You.

Julianne Cripps Clark 7-September-2022