Applies his knowledge to the problem in the scene.
Technical support · Characters
10 / 31OUR SERIES / CHARACTERS
Francisco “Paco” Aguirre
He champions collective autonomy and remembers how the systems work; his challenge is to distinguish useful experience from habit.
Continue reading
PROPOSED VISUAL01
Character · profile and arc
He champions collective autonomy and remembers how the systems work; his challenge is to distinguish useful experience from habit.
An ordinal editorial scale for fiction writing; it is not an assessment or measurement. Values and future states are proposals; no confirmed progress is recorded.
- 01
Starting point · proposal
He may resist a change that disrupts his routine.
He champions collective autonomy and remembers how the systems work; his challenge is to distinguish useful experience from habit.
PROPOSAL - 02
Trial · hypothesis
Small experiment
Test an alternative without losing sight of why the previous step existed.
PROPOSED ARC - 03
Pace · nonlinear
Progress with setbacks
These trials are possible scenes; this profile records no confirmed episode progress.
NO CONFIRMED PROGRESS
- Strength
Institutional memory
- Tension
He may resist a change that disrupts his routine.
- Narrative challenge
Test an alternative without losing sight of why the previous step existed.
- Assembly-minded unionist
Paco defends equality; as a new proposal, he tries to keep privileges while sharing obligations.
Enlarge original ↗02
Visual guide · proposal
The visual identity remains a proposal; the sheets serve as documentation and do not approve the animation.
Enlarge original ↗03
Recorded relationships
9 direct ties and 9 possible contextual encounters. The perspectives are editorial; these encounters imply neither regular contact nor events that have occurred.
Francisco “Paco” Aguirre → Diego SerranoAppreciates: Paco may value Diego linking the proposal to a priority rather than to a technical preference alone. May frustrate him: Paco is annoyed when Diego asks for speed without knowing why that check was added.
Diego Serrano → Francisco “Paco” AguirreAppreciates: Diego may value Paco remembering a field exception missing from the procedure. May frustrate him: Diego is frustrated when Paco defends the old step without comparing its results.
Friction: Diego proposes replacing a step in the incident protocol; Paco asks which specific failure the change prevents.
Possible development: They review a real case together and agree to test the change only for that type of incident. Paco keeps the exception documented; Diego stops presenting speed as the only benefit.
Francisco “Paco” Aguirre → Maribel SalcedoAppreciates: Paco values Maribel turning oral history into a record others can consult. May frustrate him: Paco worries that Maribel will turn every exception into a permanent rule.
Maribel Salcedo → Francisco “Paco” AguirreAppreciates: Maribel values Paco being able to explain the history behind a procedure that seems arbitrary. May frustrate her: Maribel is annoyed when Paco relies on “we have always done it this way” without providing the case.
Friction: Maribel finds an unjustified exception in the file; Paco remembers the incident that led to that step.
Possible development: They check whether the original risk still exists. Maribel records the exception and its reason, and Paco agrees to review the step when conditions change.
Francisco “Paco” Aguirre → Nicolás “Nico” LinAppreciates: Paco may value Nico checking whether the old tool still does its job. May frustrate him: Paco is annoyed when Nico presents a technical test without explaining its effect on the service.
Nicolás “Nico” Lin → Francisco “Paco” AguirreAppreciates: Nico may value Paco knowing historical failures missing from the technical documentation. May frustrate him: Nico is annoyed when Paco uses a meeting to delay a change he has already tested.
Friction: Nico prepares to migrate the old system, and Paco refuses to approve it until they review the incident that led to the protocol.
Possible development: They include the historical exception in the migration test. Nico shows whether the new system covers it, and Paco accepts the change if it does not leave the service exposed.
Francisco “Paco” Aguirre → Sonia CárdenasAppreciates: Paco may value Sonia trying to reduce work that no longer adds security. May frustrate him: Paco is annoyed when Sonia removes a check before reviewing which risk it covers.
Sonia Cárdenas → Francisco “Paco” AguirreAppreciates: Sonia may value Paco distinguishing necessary protection from empty paperwork. May frustrate her: Sonia is tired of Paco defending every inherited step as if it were essential.
Friction: Sonia wants to remove a duplicate closing step, and Paco remembers that this check caught errors in the past.
Possible development: They look up the historical failure and compare the checks. If the risk is covered, Sonia removes the duplicate; if not, Paco agrees to define a lighter version.
Francisco “Paco” Aguirre → Julián FerrerAppreciates: Paco may value Julián giving the people who carry out the process a voice before changing it. May frustrate him: Paco is annoyed by moving cards around without anyone checking the actual work.
Julián Ferrer → Francisco “Paco” AguirreAppreciates: Julián may value Paco preserving the practical reason for old checks. May frustrate him: Julián finds it difficult when Paco frames every objection as a veto instead of a testable condition.
Friction: Julián calls a session to redesign the procedure, and Paco insists on recording why each step exists.
Possible development: They replace the workshop with a review of a specific incident. Julián ends with a decision, and Paco agrees to test it with a documented exception.
Francisco “Paco” Aguirre → Lucía RoldánAppreciates: Paco values Lucía knowing who can check access and whom to notify. May frustrate him: Paco is annoyed when Lucía confirms a route without checking whether it is available.
Lucía Roldán → Francisco “Paco” AguirreAppreciates: Lucía may value Paco spotting a practical need before the visitor arrives. May frustrate her: Lucía dislikes Paco reminding her in front of others whom she left waiting.
Friction: Paco asks Lucía for an accessible route for a visitor, and she is about to confirm it without checking the side entrance.
Possible development: Lucía checks before confirming, and Paco explains the need without exposing her mistake in front of the visitor. The route is clear, and they both preserve operational trust.
Francisco “Paco” Aguirre → Bruno MeyerAppreciates: Paco may recognize that Bruno understands the real pressure of the shifts. May frustrate him: Paco is angry when Bruno invokes “the team” to shut down a discussion the team never got to have.
Bruno Meyer → Francisco “Paco” AguirreAppreciates: Bruno may value Paco remembering how a decision affects the people doing the work. May frustrate him: Bruno is annoyed when Paco turns every instruction into a meeting.
Friction: At a shift meeting, Paco asks to review a pause in the protocol, and Bruno invokes team productivity to prevent debate.
Possible development: They agree to hear two cases from the shift and decide who will change the protocol. Bruno stops speaking for the whole team, and Paco agrees to close the discussion using a clear criterion.
Francisco “Paco” Aguirre → Tomás SalinasAppreciates: Paco may value Tomás accurately describing what a remote worker can observe. May frustrate him: Paco is annoyed when a remote diagnosis treats the environment as if it were identical to the office.
Tomás Salinas → Francisco “Paco” AguirreAppreciates: Tomás may value Paco providing the local context and exceptions that explain the failure. May frustrate him: Tomás is frustrated when field experience arrives as a list of exceptions without reproducible steps.
Friction: A field incident cannot be reproduced on Tomás’s video call, so they compare what they see from different locations.
Possible development: They record which part of the failure was observed in the field and which part could be reproduced remotely. Neither treats his own perspective as universal, and the next test has clear conditions.
Francisco “Paco” Aguirre → Celia MartínAppreciates: Paco may value Celia not overlooking wording that could make someone believe a listing is available. May frustrate him: he is irritated when she turns every procedural disagreement into a test of personal honesty.
Celia Martín → Francisco “Paco” AguirreAppreciates: Celia may value Paco remembering which step prevents an issue from recurring. May frustrate her: she is irritated when he invokes the system’s history to leave an instruction in place even though it already confuses people.
Friction: Paco’s note may preserve valuable context while describing a step that has since changed. Celia is right about transparency, but may moralize before asking a question.
Possible development: Paco updates the note with its source, and Celia states the specific correction before passing judgment; they may again treat a disagreement as a moral failing.
Enlarge original ↗