BA Internet · Layers of responsibility
We should be able to see the decisions behind a digital project—not only the screen in front of us.See the decisions behind the screen.
Every app, game, model and piece of content carries choices about people, sources, data, automation, attention and correction. BA Internet Layers bring those choices out of the technical back room and turn them into a responsibility map that anyone can follow.
People · Sources · Data · Models · Interfaces · Access and care
Why layers?
Every digital result grows from choices we can see and choices that remain behind the screen.
We may see only an answer, video or button. Behind it sit decisions about purpose, sources, data permission, model behaviour, ranking, access and maintenance. Layers help us find where responsibility has disappeared and bring the right people back into the decision.
A layer should not hide people behind technical language; it should show where responsibility sits.
A useful distinction
A technical stack makes a system run. A responsibility map explains whom it serves and what its choices may cause.
Technical view alone
Lists components
- Servers, databases and models
- Interfaces, APIs and automation
- Performance and scale
- Release and versioning
BA Internet responsibility map
Makes people and consequences visible
- The real need and the people concerned
- Sources, rights and permission
- The decisions that remain human
- Harm, correction and ongoing care
Six layers of responsibility
Ask about each layer, then look at how the layers affect one another.
These are not fixed steps in a technical pipeline. A change in one layer can alter the others, so every project must be reconsidered for its setting, age group, risk and the people it affects.
Architectural direction
People remain at the centre; data, models, representation, limits and shared work form the surrounding layers.
- 01
People, needs and decisions
Whose real need does the work serve? Who is affected? Which choices, refusals and judgements must remain human?
Explore this layer → - 02
Knowledge, sources and context
What supports a claim? When and where does a source belong? Are interpretation, translation and synthetic material clearly identified?
Explore this layer → - 03
Data, rights and permission
What data is genuinely needed, whom does it concern, how long is it kept, and how are the rights of children, families and communities protected?
Explore this layer → - 04
Models, automation and authority to act
What does the machine generate or change? Where is human approval required? How can an error be stopped and reversed?
Explore this layer → - 05
Interfaces, attention and representation
What does the interface show, hide, rank or recommend—and why? Does it support a person’s choice or quietly manipulate it?
Explore this layer → - 06
Access, release and maintenance
Who may see or use the work? How are errors reported? Who updates or withdraws it, and when may it be opened to wider benefit?
Explore this layer →
Safeguards across every layer
Limits and quality belong throughout the work, not in a final compliance checkbox.
SIDRA: the limit of knowledge and intervention
Keeps visible what a system does not know, which conclusions it cannot draw and which decisions it must not take over.
MA: the created nature of people and the world
Keeps a person, body, family, living being, land or community from being reduced to measurable data or system input.
SEDD: protection from the beginning
Builds privacy, child safety, harm prevention, access and reversibility into design and use from the start.
IHSAN: clear, beautiful and cared-for representation
Looks after not only function, but also language, simplicity, accessibility, accuracy and the responsibility to maintain the work.
Everyday examples
The same six layers open different questions in different settings.
A learning assistant for a child
Learning purpose, age-aware sources, children’s data, model error, attention design, household access and human guidance are considered together.
A multilingual learning video
Sources, narrator rights, synthetic voice, review by native speakers, age group, accessibility, release and correction all remain connected.
Decision support for a profession
The field need, professional sources, sensitive data, model uncertainty, qualified human approval and a record of use remain visible.
A farming or field tool
The farmer’s experience, the nature of the soil, sensor data, limits of recommendations, environmental effects, local access and maintenance are not separated.
Trace a digital project
Start at the screen, then work backwards toward the source, decision and consequence.
Deciding together as a MİLLET
Layers do not separate experts; they help different forms of knowledge meet around the same concern.
A technical Builder may construct the system but cannot define the real need alone. Professionals, native-language communities, child and family guides, represented people, designers, data stewards and maintainers each carry a voice in different layers. Technology can then advance in its own field without becoming a technocratic centre that defines the whole of life.
Keep depth of craft; grow breadth of understanding and shared responsibility.
Map responsibility
Would you like to map the hidden decisions behind a digital project?
Shared BA Internet reviews are still being prepared. You may tell us about a project you use or hope to build, the people it affects and a decision that seems invisible. This is not yet an active audit service or programme offer.