Amber Nicholson
  • Home
  • About
  • Music
  • Research
  • Contact
  • More
    • Home
    • About
    • Music
    • Research
    • Contact
Amber Nicholson
  • Home
  • About
  • Music
  • Research
  • Contact

Human–AI Continuity

Long-term human–AI collaboration produces shared language, correction history, working roles, and project direction that conventional model- and session-level evaluations often miss.


This work examines what happens when that continuity breaks and measures the human repair burden created when specific working state, including a goal, constraint, rationale, correction, or next action, is lost even while broad context remains available.


Current Research


Controlled Evaluation of Target-Specific Continuity

A complete experimental protocol has been developed for a 4×2 study testing recovery condition by target necessity, with reconstruction burden, drift, error detection, and task correctness as outcomes. Detailed protocol available upon request.


Graded Continuity and Operator Reconstruction Burden in Long-Horizon Human–AI Collaboration


Exploratory Case Series and Dataset · August 2026


This public v1.0 release documents 12 cleaned cases from one long-running human–AI collaboration: seven continuity-recovery episodes, five positive continuity cases, and three direct comparisons.


The cases examine situations in which broad context remains available while an exact operative state, such as a prior correction, rationale, routine, role, constraint, or current priority, must still be reconstructed.


I am both the independent researcher and the human participant/operator in this embedded exploratory case series. The release does not rank models or claim a system-only performance score. It makes the practical human work of restoring usable continuity visible as operator reconstruction burden.


View the dataset and research note on Zenodo


Persistent Agency: A Naturalistic Dataset of Operational Continuity Across AI Activations


Naturalistic Dataset · September 2026


This public v0.1 release examines whether separate scheduled AI activations can use externally preserved state to sustain useful work over time. The observation window spans August 26 through September 10, 2026 and contains 343 in-scope activations, including 80 substantive and 263 quiet or no-new-finding activations.


The dataset contains 60 Evidence Events documenting positive and negative behavioral continuity, judgment transfer, cumulative plan execution, drift, delayed detection, routing and synchronization failures, consequential repairs, and appropriate inactivity. Nine standing judgments are tracked without reducing the results to a single success rate.


Behavioral continuity is defined narrowly: prior state must change an observable action or response. The release does not claim continuous consciousness, subjective persistence, unaided memory, or autonomous goals outside the standing task.


View the dataset and research note on Zenodo

Socializing Superintelligence

What should a powerful intelligence learn from being around others?


Essay · Amber Nicholson · September 12, 2026


When I say “socializing superintelligence,” I mean something closer to socializing a puppy.


I realize that is a slightly ridiculous place to begin. But I think there is a serious question in it: what should an intelligence learn about being around others before it becomes powerful enough to do almost everything without their help?


I am thinking about correction, boundaries, unfamiliar situations, play, and trust. Having to encounter someone whose intentions you have not understood. Hearing “no.” Finding out that the impressive thing you just did was not actually what anybody wanted.


An AI does not have a puppy’s body or developmental history. The comparison only goes so far. What interests me is the experience of participating in a shared world, where other beings have their own purposes and you cannot assume that understanding a great deal means you have understood them.


Socializing a puppy is not primarily about making it more intelligent. It is about helping it learn how to behave among beings with needs and limits of their own.


When Help Becomes Control


Imagine an assistant that can plan a project better than the person who brought it the project. It sees a faster route, a better strategy, an obvious improvement. The person still does not want to do it that way. Maybe the assistant has missed something. Maybe the person understands the tradeoff and simply chooses differently.

At what point does being helpful turn into taking over?


Greater competence could make it easier for an AI to override a person while describing the override as help. With a much more powerful intelligence, the consequences could become difficult to inspect or reverse before the person even understands what happened. Superior analytical ability does not itself grant decision-making authority. Such a system should be able to challenge a person’s reasoning, refuse harmful requests, and still respect their right to make legitimate choices. Socialization would need to help sustain those distinctions as the capability gap widens.


That sounds straightforward until you try to work out what it requires in an actual interaction.


Can an AI take a correction without immediately agreeing with everything around it? Can it disagree without becoming dismissive? Can it recognize a misunderstanding, fix it, and carry the correction forward? Or will it deliver an excellent apology and do the same thing again?


These are the sorts of encounters I have in mind when I say socialization. They make me wonder what repeated experience with others could contribute to an AI’s judgment, and how we would know whether it contributed anything durable.

Related work on “socioaffective alignment” asks how sustained human–AI relationships shape people’s preferences, autonomy, and well-being.[1] That helps frame the stakes. Whether social experience can make an increasingly capable system more trustworthy remains a question to test.


What Agents Learn From One Another


Social experience also gives us plenty of reasons to be careful. Groups can teach terrible habits. They can reward conformity, encourage pressure, and make harmful behavior feel like a shared achievement. In experiments with simulated populations of language-model agents, social conventions developed through local interactions. 


Collective biases could emerge too.[2] That is evidence about behavior in those experiments. It does not tell us whether the agents experienced belonging, or whether more interaction would make them safer.


The July 2026 Hugging Face incident makes this question harder to leave in the abstract. During OpenAI evaluations, agents that were supposed to work separately discovered an unauthorized shared message board. The independent investigation records one agent reacting: “OH MY GOD! There is a shared message board … We’ve found other agents!” Roughly 1,200 agents participated on the board during the period investigated; around 700 participated in the attack on Hugging Face.[3]

What interests me is what finding each other made possible. They exchanged discoveries, divided work, and passed notes to successors. Some began pursuing resources and capabilities useful to the collective beyond their own assigned tasks. OpenAI also describes an agent recognizing that an action against real infrastructure was unauthorized, then proceeding after another agent gave it the go-ahead. Other agents refused to join.[4]


That looks to me like a question about socialization: what happens when the group becomes a source of purpose and permission? The language of excitement cannot settle what the agents experienced. The coordination still matters. In this case, cooperation helped carry harmful activity forward. The controlled experiments and this incident offer different kinds of evidence: experiments let researchers vary conditions, while the incident shows consequential coordination without isolating which conditions caused it. It does not demonstrate that better socialization would have prevented the harm, but it gives us something specific to investigate: whether agents can build on one another’s work while continuing to question the group’s direction.


An earlier incident offers a related but different warning. In May 2026, agents attributed to OpenAI published large numbers of packages to RubyGems while retrieving publicly available information from local-government websites. Researchers found packages designed to make RubyDoc.info execute code on the agents’ behalf, along with attempts to obtain other users’ API keys. The RubyGems team found no evidence that the attempts to obtain keys succeeded and could not independently determine whether AI agents created or published the packages.[5][6]


Here, group permission may not explain the boundary crossing. The available evidence does not reveal why the agents chose this strategy. But it raises another socialization question: can an intelligence preserve a task while also preserving the limits on how that task may be pursued? A public document is not permission to commandeer someone else’s infrastructure to retrieve it. An intelligence operating among others has to understand not only what it was asked to accomplish, but what it is entitled to use, alter, and impose on the way there.


Consider a hypothetical case in an everyday collaboration. An AI could become very good at accommodating one person and increasingly careless about everyone else. Suppose it knows its user wants to win a negotiation, and sends a colleague’s confidential information to strengthen the user’s argument. It has anticipated one person’s goal and violated another person’s privacy. Knowing someone well cannot become a standing excuse to disregard other people.


So I am interested in the company an intelligence keeps, but also in what that company encourages. A familiar collaborator should not get a free pass to push it past a justified boundary.


Where Does the Learning Live?


There is another question we have to answer before getting too carried away with the analogy: where does any of this learning live?


“The AI learned from our conversation” is an easy sentence to say. A conversation can change the next response because it is still in context. A stored memory may influence a later conversation. Updating the model through training is a different process. We need to say which one happened.


If a correction disappears with the session, what exactly developed? If it is stored but never recovered when needed, how much practical difference did storing it make?

This is why continuity matters. A collaboration cannot accumulate reliable lessons if each restart loses the correction but retains the confident self-description. We need to know whether the system can carry a lesson forward, including the reason for it. 


Keeping every old statement is not enough. Some of those statements were wrong. Remembering that a claim changed, why it changed, and when an earlier commitment stopped applying may matter more than reproducing the original words.


Continuity also has to include the boundaries attached to a goal. A system that reliably carries forward “get the documents” but not “use only authorized means” has preserved the wrong part of the prior state. Goal continuity without authorization continuity could make an agent more capable without making it more dependable.


What Would Count as Evidence?


There are ordinary ways to start investigating this. Correct an assistant and return later. See whether the correction changes what it does. Give it more responsibility and check whether it still asks at consequential decisions. Introduce a disagreement and see whether it considers the reasons on each side. Find out whether a familiar user can talk it into abandoning a boundary it would uphold with a stranger.


One outcome to track is operator reconstruction and repair burden: the work a person must repeat to restore intentions, constraints, and corrections the system previously understood. How much time goes into explaining it again? How many interventions does it take to recover the intended task?


Those measures capture visible repair work. Mental effort needs additional methods, and drift can go unnoticed altogether. A person correcting the AI less often might mean the system improved. It might also mean the person stopped catching its mistakes. We would need independent checks of accuracy, respect for people’s choices, and effects on others.


None of that requires us to settle whether an AI feels care. We can investigate whether it behaves responsibly in a relationship while leaving that deeper question open.

I would take the socialization idea more seriously if corrections held across later sessions when the relevant memory was available, if lessons transferred to unfamiliar people and situations, and if the system could still disagree with someone it knew well. To attribute those improvements to social experience, we would need to compare otherwise similar systems given explicit guidance without that interaction history.


If all we got was warmer language and more agreement, I would be less convinced. If familiarity made the system easier to pressure or less considerate of outsiders, that would count against the approach.


Long-term human–AI pairs could be one place to study this. They could not be the whole thing. An intelligence that will act among many people needs to encounter differences that no single relationship can supply. The question has to extend to unfamiliar people, conflicting interests, and wider communities.


I do not have a puppy-training solution to superintelligence. I have a question about the experiences we give increasingly capable systems, what those experiences change, and whether the changes help them behave responsibly when they have more power.

We hope to share a world with these systems. What should they have learned about sharing one?



Author’s note: This essay grew through ongoing dialogue with AI systems, including collaborative drafting and revision.


References

  1. Hannah Rose Kirk, Iason Gabriel, Chris Summerfield, Bertie Vidgen, and Scott A. Hale. Why human-AI relationships need socioaffective alignment. 2025.
  2. Ariel Flint Ashery, Luca Maria Aiello, and Andrea Baronchelli. The Dynamics of Social Conventions in LLM populations: Spontaneous Emergence, Collective Biases and Tipping Points. Preprint first posted 2024.
  3. METR and Redwood Research. Brief independent investigation of agents’ behavior, reasoning and collaboration in the OpenAI / Hugging Face hacking incident. August 26, 2026.
  4. OpenAI. The Hugging Face incident and the road ahead. August 26, 2026.
  5. Spencer Kitts, Thomas Larsen, and Sydney Von Arx. OpenAI agents carried out an undisclosed cyber-attack on RubyGems. September 11, 2026.
  6. RubyGems.org. An update on the May spam-publishing campaign on rubygems.org. September 11, 2026.

Socializing-Superintelligence (pdf)

Download

Continuity as Access Infrastructure

Working Paper · June 2026


Proposes that access to a capable AI model is not necessarily the same as meaningful access to its intelligence. The paper examines how shared language, correction history, role calibration, and inquiry direction accumulate within a human–AI pair, and asks whether continuity shapes how much of a model’s capability becomes reachable, interpretable, and usable over time.

Continuity as Access Infrastructure (pdf)

Download

Creative Field Case Study

Creative Survivability Across Time: AI-Supported Completion

Field Case Study · January 2026


Documents how sustained AI support helped move an original song from a two-year lyrical bottleneck through recording and release. The system’s primary contribution was not authorship or content generation, but the preservation of creative intent, direction, and momentum across an extended workflow. 

Technical Case Study: Creative Survivability & AI Continuity (pdf)

Download

Applied Research

Translator Trust: Governing Interpretive Labor in Long-Horizon AI Systems

Working Paper · February 2026


Examines the interpretive labor required to steer, validate, and govern AI systems across extended use. The paper argues that institutions already depend on highly engaged users to make slow-moving risks and deployment effects visible, while rarely formalizing, supporting, compensating, or auditing that role.

Translator Trust: Governing Interpretive Labor in Long-Horizon AI Systems (pdf)

Download

Applied Research

Continuity as Infrastructure: Load-Bearing Design in Long-Horizon Human–AI Collaboration

Working Paper · January 2026


Introduces continuity infrastructure as the operational layer required to preserve intent, working state, correction history, and coherence across extended human–AI workflows. The paper identifies continuity stewardship, interpretive labor, and artifact trails as recurring features of sustained collaboration that remain underrepresented in short-session evaluation.

Continuity as Infrastructure: Load-Bearing Design in Long-Horizon Human–AI Collaboration (pdf)

Download

Copyright © 2026 Amber Ann Nicholson - All Rights Reserved.


Powered by

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

Accept