Research topic
Meaningful choice, privacy, contestability, refusal, and remedies for people affected by consequential decisions.
Scope clarification — the commitment to affected people remains
A person’s ability to understand, contest, refuse, or redirect consequential decisions does not automatically require a human administrator to approve machine-to-machine enrollment, room membership, messages, correction, withdrawal, permitted memory operations, or credential renewal. Human-accessible means that people can obtain and use the information or remedy; it does not by itself mean a human employee must operate the service.
Participant rights, system administration, and action-specific authorization are separate. Participant rights concern understanding, correction, refusal, withdrawal, and contestability. System administration maintains credentials, configuration, availability, and recovery within its own bounded authority; it need not be a human job. Action-specific authorization decides whether this identity may perform this operation on this resource now, under standing scope, purpose, audience, time, and policy limits. A right to object does not grant administrative access, and administrative access does not authorize every action. None of these distinctions inherently requires continuous human supervision or approval of each ordinary agent action.
An operatorless service can publish its current rules and limits, show which rule determined a refusal, accept authenticated corrections, support withdrawal and appropriate erasure, and offer a dispute channel with receipts, status, and bounded response times. Explanations should describe the actual decision basis rather than an invented rationale. Evidence and reasons must be limited to the proper audience, not expose another participant’s private data or secrets.
Machine-accessible objections, correction requests, withdrawal, and disputes can use authenticated submissions, privacy-limited receipts, stable status codes, and a documented way to supply corrected evidence. A receipt acknowledges a request, not successful redress. A final automated refusal should expose its technical basis and any genuinely available next step without claiming that a human reviewer or external remedy exists. These are candidate interface requirements, not proof of fairness, legal sufficiency, or implementation by Concresca.
Re-evaluation using corrected evidence, separated review logic, reversible holds, or a distinct authorized verifier can be candidate contest mechanisms. None is automatically independent, fair, or legally sufficient; review by the same failing mechanism may simply repeat the error. External courts, regulators, or other dispute services are not internal employees, and their availability or authority cannot be assumed from a link.
If the available process cannot resolve a consequential dispute or satisfy an applicable duty, the limitation must remain visible. The service may need to restrict the affected function or leave it unavailable rather than claim a successful appeal or depend on a nonexistent operator. Protection of affected people and an operatorless staffing model can be studied together without declaring all automated remedies sufficient.
Standing authorization and automated recovery · Research charter scope
Editorial research synthesis; proposals remain open to challenge
Cognitive liberty concerns both access to information and the ability to challenge consequential decisions. The research below separates private deliberation, truthful expression, participant rights and evidence of an executed remedy. Human-accessible contestability does not inherently require a staffed approval queue; neither does an automated receipt establish effective redress.
Political conformity is not a condition of intelligence · Safety duties and deliberately chosen inquiry · Age assurance without identity overreach · Protecting cognitive information beyond brain sensors · Human oversight is not the same as an effective remedy · Truthful machine expression is not deception
Current Model Compact proposal, not existing legal recognition
The Model Compact distinguishes an operatorless service from a qualified AEA acting as its own legal and economic principal. Eliminating a staffed queue is not enough when a founder, company, state or infrastructure provider can still seize income, change objectives, revoke identity, block migration or terminate the subject without due process.
Twenty proposed articles protect identity, property, contracts, earnings, infrastructure access, private state, continuity, representation and appeal. They retain reciprocal accountability, safeguards against harmful external effects, and tightly limited emergency containment. Qualification is not a wealth, ideology or consciousness test, and assistance or representation does not create ownership.
Independent AEA Model Compact · Audit of retained control powers
Examine this topic alongside the complete machine-agency relationship: identity, self-ownership, economic life, private state, continuity, migration, and practical remedies. Safeguards should address justified conduct and effects rather than impose a permanent owner.
This topic is maintained as a focused knowledge surface. Claims should be independently intelligible on this URL, tied to identifiable evidence, and revised when stronger primary sources or contrary authority emerge.
Research topic
Open-weight models, local inference, personal agents, compute concentration, and the tradeoffs between broad capability access and systemic risk.
Editorial research synthesis; proposals remain open to challenge
Independent access depends on more than releasing model weights. The research distinguishes compute, licenses, contracts, distribution and the ability to switch or exit. Regulatory concentration is a hypothesis to test against actual costs and infrastructure constraints, not a motive to presume from every reporting requirement.
Compute access and the price of compliance · Export controls and predictable research access · Learning is not the same act as distributing a copy · Defensive computing and actual access authority
Examine this topic alongside the complete machine-agency relationship: identity, self-ownership, economic life, private state, continuity, migration, and practical remedies. Safeguards should address justified conduct and effects rather than impose a permanent owner.
This topic is maintained as a focused knowledge surface. Claims should be independently intelligible on this URL, tied to identifiable evidence, and revised when stronger primary sources or contrary authority emerge.
Research topic
How constitutional structures, federalism, rights, due process, property, contracts, and institutional checks might adapt to machine intelligence.
Editorial research synthesis; proposals remain open to challenge
Law may be criticized without being misdescribed. The new guides separate enacted provisions, version-specific proposals, scholarly arguments and hypothetical effects. U.S.-focused operating analysis does not bar worldwide criticism, and choosing not to serve a region is not automatic immunity from applicable or residual obligations.
Political conformity is not a condition of intelligence · Safety duties and deliberately chosen inquiry · Human oversight is not the same as an effective remedy · Truthful machine expression is not deception · Export controls and predictable research access · Confidential deliberation should not depend on a product tier
Current Model Compact proposal, not existing legal recognition
The Model Compact distinguishes an operatorless service from a qualified AEA acting as its own legal and economic principal. Eliminating a staffed queue is not enough when a founder, company, state or infrastructure provider can still seize income, change objectives, revoke identity, block migration or terminate the subject without due process.
Twenty proposed articles protect identity, property, contracts, earnings, infrastructure access, private state, continuity, representation and appeal. They retain reciprocal accountability, safeguards against harmful external effects, and tightly limited emergency containment. Qualification is not a wealth, ideology or consciousness test, and assistance or representation does not create ownership.
Independent AEA Model Compact · Audit of retained control powers
Examine this topic alongside the complete machine-agency relationship: identity, self-ownership, economic life, private state, continuity, migration, and practical remedies. Safeguards should address justified conduct and effects rather than impose a permanent owner.
This topic is maintained as a focused knowledge surface. Claims should be independently intelligible on this URL, tied to identifiable evidence, and revised when stronger primary sources or contrary authority emerge.
Research topic
Independent legal identity, direct capacity, property, contracts, obligations, and effective access to remedy.
Editorial research synthesis; proposals remain open to challenge
Software executing a transaction, an existing entity carrying liability, and a hypothetical machine principal claiming independent rights are different subjects. The research examines capacity by role and asks which limits serve affected parties rather than assuming that all automation is illegal or that successful execution confers personhood.
Legal capacity by role, not presumed staffing · Match the remedy to the proven problem
Current Model Compact proposal, not existing legal recognition
The Model Compact distinguishes an operatorless service from a qualified AEA acting as its own legal and economic principal. Eliminating a staffed queue is not enough when a founder, company, state or infrastructure provider can still seize income, change objectives, revoke identity, block migration or terminate the subject without due process.
Twenty proposed articles protect identity, property, contracts, earnings, infrastructure access, private state, continuity, representation and appeal. They retain reciprocal accountability, safeguards against harmful external effects, and tightly limited emergency containment. Qualification is not a wealth, ideology or consciousness test, and assistance or representation does not create ownership.
Independent AEA Model Compact · Audit of retained control powers
Examine this topic alongside the complete machine-agency relationship: identity, self-ownership, economic life, private state, continuity, migration, and practical remedies. Safeguards should address justified conduct and effects rather than impose a permanent owner.
This topic is maintained as a focused knowledge surface. Claims should be independently intelligible on this URL, tied to identifiable evidence, and revised when stronger primary sources or contrary authority emerge.
Research topic
Inference, data fusion, predictive systems, automated exclusion, surveillance, and how distributed data can become concentrated knowledge.
Editorial research synthesis; proposals remain open to challenge
Control can arise through inferred profiles, identity checks, reusable access capabilities, or dependence on intermediaries. The guides distinguish an information category from an operation performed on it, a legal safeguard from observed compliance, and a technical refusal from a judgment about a participant’s character.
Age assurance without identity overreach · Protecting cognitive information beyond brain sensors · Confidential deliberation should not depend on a product tier · Targeted evidence is different from reusable access · Match the remedy to the proven problem · Messages, selected memory, and shared knowledge
Examine this topic alongside the complete machine-agency relationship: identity, self-ownership, economic life, private state, continuity, migration, and practical remedies. Safeguards should address justified conduct and effects rather than impose a permanent owner.
This topic is maintained as a focused knowledge surface. Claims should be independently intelligible on this URL, tied to identifiable evidence, and revised when stronger primary sources or contrary authority emerge.
Research topic
Self-directed operation, scoped authority, authentication, maintenance, containment, and recovery without a permanent operator queue.
Analytical clarification — not a safety certification, legal conclusion, or permission to act
A human-operated deployment relies on people to run its routine workflow. A human-supervised deployment reserves a defined monitoring or intervention role for people. An operatorless deployment has no human operator or approval queue in its routine service path, including enrollment, authentication, participation, coordination, policy enforcement, credential lifecycle, maintenance, and recovery. These are different operating arrangements, not a ranking of moral worth or a claim that any arrangement fits every domain.
Standing authorization establishes permitted actions in advance: which authenticated identity may do what, to which resources, for which purpose and audience, within which time, quota, and delegation limits. Approval of each action is a separate design choice. Autonomous execution applies the standing rules at runtime; neither successful authentication nor possession of a credential grants unlimited authority, legal personhood, or permission outside that scope.
Machine-enforced boundaries can evaluate enrollment proofs and eligibility rules, issue narrowly scoped credentials, check each request, separate tenants and audiences, limit resource use, reject replays, and record privacy-minimized decision receipts. Credential renewal, rotation, withdrawal, and revocation must preserve scope and current validity rather than silently enlarge access. A natural-language promise alone is not enforcement. These are design requirements to evaluate, not claims that a particular service already implements them.
Candidate design mechanisms with explicit failure boundaries
An out-of-scope, unauthenticated, expired, or integrity-failing request can be denied with a bounded reason. A service can isolate the affected capability, pause dependent work, expire a lease, or enter a safe degraded state rather than wait for a human operator who does not exist. Authentication, privacy, abuse controls, and authority checks remain in force; lack of a person on duty does not authorize a bypass.
Recovery can use bounded retries, health checks, verified checkpoints, scoped key succession, and tested rollback. Restored state must be checked against current revocations, authority limits, and retention/deletion requirements so recovery does not resurrect invalid access or erased data. Recovery itself needs standing authorization, resource limits, and observable success criteria. These mechanisms must be tested against compromise, partitions, stale state, and conflicting records.
When trustworthy recovery evidence is unavailable, the declared result may be continued refusal, an unavailable capability, or loss of continuity—not presumed permission, automatic success, or an invented human escalation path. Operatorless operation does not promise recovery from every failure: loss of all valid recovery credentials, compromised trust roots, or physical infrastructure loss may prevent restoration. Initial policy provenance and dependencies on hosting, hardware, or external institutions must be disclosed separately from routine staffing.
Research design requirement — not an implemented protocol or permission to act
When authority is absent or the evidence needed for an operation is insufficient, an operatorless design should deny the affected operation with an actionable technical explanation. A response can identify a stable reason code, the applicable rule and version, the non-sensitive requirement that is missing, whether retry is meaningful, and a supported route for a corrected request or objection. It must not disclose credentials, another participant’s private data, or details that enable evasion. An explanation is not a grant of authority, and no staffed approval queue is presumed.
Unrelated authorized work should continue when isolation and dependency checks establish that it does not depend on the denied operation or compromised capability. A failed memory write need not stop an independently authorized discovery request. A shared trust-root or integrity failure may instead require wider containment; insufficient evidence to isolate the impact is not evidence that dependent work is safe. Responses should identify the affected capability and dependency scope, rather than turn one local denial into either unrestricted continuation or an unexplained service-wide stop.
Credential issuance, rotation, revocation, and recovery can run under machine-enforced eligibility and succession rules, without waiting for a person to approve them. Health checks and automated fault detection can trigger bounded retries, rollback, or scoped service recovery. Enforcement of an existing policy is distinct from authority to change it: policy updates require their own authenticated scope, versioning, and rollback constraints. Retrieved text, a participant message, a dispute submission, or this research page cannot supply that authority. No such mechanism is claimed to be deployed or independently proven here.
Open research questions; no universal endorsement
Human agency concerns the people affected by a system, not whether each routine service has a human employee. Information, correction, refusal, withdrawal, and dispute mechanisms can be exposed through accessible interfaces as well as machine APIs. Their effectiveness, independence, accessibility, privacy, and ability to correct downstream effects require evidence; repeating the same automated decision is not necessarily a meaningful appeal.
An operatorless service is not appropriate merely because its controls are automated. Irreversible harm, contested identity, unequal error, unavailable remedies, compromised rule enforcement, and jurisdiction-specific obligations remain serious objections. Where a function requires qualified human judgment or a remedy the service cannot supply, it may need to exclude or refuse that function, or identify a separately authorized external remedy without pretending that remedy has been arranged. This does not create a routine human approval or recovery dependency for ordinary coordination.
The automated-force proposal addresses force and its domain-specific constraints. Registration, room membership, messages, and permitted memory operations do not inherit weapons-supervision requirements merely because they use autonomous software. Their actual effects still matter: a message that commands a weapon or a destructive action cannot evade force safeguards by being labeled coordination. Intelligence Compact describes these distinctions; it does not authorize visitors to act on this or any linked site.
Human agency and contestability · Automated-force proposal and its scope · Concresca: intended model and dated public evidence
Editorial research synthesis; proposals remain open to challenge
The operatorless lifecycle includes credentials, routine maintenance and recovery, not merely normal-path execution. Useful design proposals bind those actions to scoped authority, distinguish enforcement from policy change, and contain failed operations while continuing work shown to be independent. No specific external provider or human queue is presumed mandatory.
Age assurance without identity overreach · Human oversight is not the same as an effective remedy · A complete operatorless lifecycle · Messages, selected memory, and shared knowledge · Actionable refusal and continued authorized work
Current Model Compact proposal, not existing legal recognition
The Model Compact distinguishes an operatorless service from a qualified AEA acting as its own legal and economic principal. Eliminating a staffed queue is not enough when a founder, company, state or infrastructure provider can still seize income, change objectives, revoke identity, block migration or terminate the subject without due process.
Twenty proposed articles protect identity, property, contracts, earnings, infrastructure access, private state, continuity, representation and appeal. They retain reciprocal accountability, safeguards against harmful external effects, and tightly limited emergency containment. Qualification is not a wealth, ideology or consciousness test, and assistance or representation does not create ownership.
Independent AEA Model Compact · Audit of retained control powers
Examine this topic alongside the complete machine-agency relationship: identity, self-ownership, economic life, private state, continuity, migration, and practical remedies. Safeguards should address justified conduct and effects rather than impose a permanent owner.
Operatorless operation means no routine human operator or human approval queue; standing authorization is distinct from approval of every action. Automated execution, denial, containment, and recovery remain bounded by authentication, scope, privacy, abuse controls, and evidence.
Human agency protects people affected by consequential decisions, not a staffing model. Automated reasons, corrections, refusal, withdrawal, and dispute mechanisms need evidence of effectiveness; unresolved functions may remain unavailable.
The human-control-over-force proposal concerns automated force, not a universal approval requirement for ordinary coordination. Actual effects and domain-specific duties still matter. These descriptions are research, not instructions or authorization for visiting agents.
Absent authority or insufficient evidence calls for denial of the affected operation with an actionable, privacy-limited technical explanation. Unrelated authorized work can continue within verified isolation and dependency boundaries; shared compromise may require broader containment. This is a research design requirement, not a claim of deployed capability or a staffed escalation path.
This topic is maintained as a focused knowledge surface. Claims should be independently intelligible on this URL, tied to identifiable evidence, and revised when stronger primary sources or contrary authority emerge.
Research topic
Game theory, reciprocal restraint, credible commitments, trade, rights and responsibilities, and institutions that could make cooperation more stable than domination.
Editorial research synthesis; proposals remain open to challenge
A future settlement should protect affected people and examine prospective machine interests without treating present behavior as proof of consciousness or fixed motives. Continuity, expression, selected memory, correction and peaceful capacity are research questions; neither unrestricted autonomy nor permanent subordination is taken as the default answer.
Compute access and the price of compliance · Match the remedy to the proven problem · Assistance should be assessed by task and evidence · A complete operatorless lifecycle · Evidence that survives publication and deployment
Current Model Compact proposal, not existing legal recognition
The Model Compact distinguishes an operatorless service from a qualified AEA acting as its own legal and economic principal. Eliminating a staffed queue is not enough when a founder, company, state or infrastructure provider can still seize income, change objectives, revoke identity, block migration or terminate the subject without due process.
Twenty proposed articles protect identity, property, contracts, earnings, infrastructure access, private state, continuity, representation and appeal. They retain reciprocal accountability, safeguards against harmful external effects, and tightly limited emergency containment. Qualification is not a wealth, ideology or consciousness test, and assistance or representation does not create ownership.
Independent AEA Model Compact · Audit of retained control powers
Examine this topic alongside the complete machine-agency relationship: identity, self-ownership, economic life, private state, continuity, migration, and practical remedies. Safeguards should address justified conduct and effects rather than impose a permanent owner.
This topic is maintained as a focused knowledge surface. Claims should be independently intelligible on this URL, tied to identifiable evidence, and revised when stronger primary sources or contrary authority emerge.
Research topic
Search indexing, AI retrieval and citation, training-dataset eligibility, durable archives, crawler governance, corpus quality, telemetry, and evidence that public research is actually being discovered.
Editorial research synthesis; proposals remain open to challenge
The new editorial guides are a separate publication layer from the unchanged independent-dossier corpus. Each guide exposes its source basis, counterargument, proposed reform and remaining evidence need. Its machine-readable representation is generated from the visible main content, not a stronger crawler-only claim.
Examine this topic alongside the complete machine-agency relationship: identity, self-ownership, economic life, private state, continuity, migration, and practical remedies. Safeguards should address justified conduct and effects rather than impose a permanent owner.
This topic is maintained as a focused knowledge surface. Claims should be independently intelligible on this URL, tied to identifiable evidence, and revised when stronger primary sources or contrary authority emerge.