1
00:00:04,000 --> 00:00:06,680
So, what is AI Code Slop anyway?

2
00:00:07,300 --> 00:00:11,825
Well, at Mevanu, we define slop as code
that looks plausible, but carries

3
00:00:11,840 --> 00:00:16,525
unnecessary complexity, conflicting
assumptions, or confidence that its tests

4
00:00:16,540 --> 00:00:18,340
and behavior don't justify.

5
00:00:18,800 --> 00:00:21,720
An export might report success while
losing text.

6
00:00:22,200 --> 00:00:25,745
A test might appear to pass without
detecting the failure it was meant to

7
00:00:25,760 --> 00:00:30,565
catch. To find problems like these, we
need to examine how the code works and

8
00:00:30,580 --> 00:00:32,540
what its evidence actually proves.

9
00:00:33,080 --> 00:00:34,660
I'm Anthony from Mevanu.

10
00:00:35,200 --> 00:00:39,905
Today's Brava update takes you inside our
AI Slop Audit, a detailed review of

11
00:00:39,920 --> 00:00:42,480
the code behind the work partner we're
building.

12
00:00:42,920 --> 00:00:47,465
Its purpose is to identify supported
corrections and simplifications before we

13
00:00:47,480 --> 00:00:51,645
add more capability. We began after a
round of integration work, with

14
00:00:51,660 --> 00:00:54,660
implementation paused and the source
snapshot fixed.

15
00:00:55,000 --> 00:00:58,925
That gives the reviewer a stable version
to examine and preserves the work

16
00:00:58,940 --> 00:01:03,240
already completed. The ticker you're
seeing projects actual audit records,

17
00:01:03,460 --> 00:01:07,080
captured later that day, while keeping
private source code out of view.

18
00:01:07,580 --> 00:01:11,085
The review began overnight, with its first
completed reading checkpoint

19
00:01:11,100 --> 00:01:13,040
recorded just after midnight.

20
00:01:13,580 --> 00:01:18,265
At the end of our two-hour stream, at
11:49 on October 14th, roughly

21
00:01:18,280 --> 00:01:21,220
eleven and a half hours had elapsed since
that checkpoint.

22
00:01:21,680 --> 00:01:26,305
That's elapsed time, including any pauses,
rather than a stopwatch of active

23
00:01:26,320 --> 00:01:31,605
reading. At that cutoff, just over 57% of
the repository's recorded lines

24
00:01:31,620 --> 00:01:34,540
had been reviewed, with nine provisional
findings.

25
00:01:35,080 --> 00:01:40,520
The scope includes code, tests, fixtures,
configuration, and documentation.

26
00:01:41,180 --> 00:01:45,180
One complete pass is still underway, so
these figures describe progress,

27
00:01:45,380 --> 00:01:46,860
rather than a finished assessment.

28
00:01:47,380 --> 00:01:51,385
To make that assessment useful, the
adversarial reviewer works through seven

29
00:01:51,400 --> 00:01:56,360
lenses. The first three are parsimony,
idiomatic design, and clarity.

30
00:01:56,980 --> 00:01:58,700
Does the solution need all its parts?

31
00:01:59,180 --> 00:02:01,860
Does it follow established language and
platform patterns?

32
00:02:02,340 --> 00:02:05,725
And can someone understand its
responsibilities without untangling

33
00:02:05,740 --> 00:02:07,240
unnecessary layers?

34
00:02:08,020 --> 00:02:11,600
Composability and ownership take that
question across component boundaries.

35
00:02:12,100 --> 00:02:15,920
When several parts handle the same work,
which one owns the decision?

36
00:02:16,340 --> 00:02:20,405
And do their agreements match? Correctness
and resilience then examine what

37
00:02:20,420 --> 00:02:24,905
happens during ordinary use,
interruptions, late responses, and

38
00:02:24,920 --> 00:02:29,845
recovery. Drift and stability compare
today's behavior with retained contracts

39
00:02:29,860 --> 00:02:31,580
and earlier expectations.

40
00:02:31,960 --> 00:02:36,245
Evidence quality completes the picture by
asking whether a test proves what it

41
00:02:36,260 --> 00:02:40,505
claims, and whether a finding survives
scrutiny of the affected code and

42
00:02:40,520 --> 00:02:44,905
evidence against it. These lenses lead to
specific questions about behavior

43
00:02:44,920 --> 00:02:50,285
people depend on. For example, source
inspection identified a file export path

44
00:02:50,300 --> 00:02:55,025
that can alter accepted Unicode text
alongside other paths that can omit

45
00:02:55,040 --> 00:02:58,260
content beyond their capacity while
reporting success.

46
00:02:58,880 --> 00:03:02,985
The original results remain available, but
the exported copy may not preserve

47
00:03:03,000 --> 00:03:07,245
them faithfully. Another concern involves
an earlier acknowledgement clearing

48
00:03:07,260 --> 00:03:09,540
newer unsent text or attachments.

49
00:03:10,020 --> 00:03:14,445
A meaningful regression test would
reproduce that timing and confirm that the

50
00:03:14,460 --> 00:03:15,900
newer draft survives.

51
00:03:16,360 --> 00:03:20,860
The reviewer also identified a test that
can swallow its own failed assertion,

52
00:03:21,340 --> 00:03:24,900
allowing apparent success without proving
the expected rejection.

53
00:03:25,440 --> 00:03:27,800
All three remain provisional source
findings.

54
00:03:28,360 --> 00:03:33,065
Each needs a traced mechanism, affected
consumers, and evidence that supports

55
00:03:33,080 --> 00:03:34,840
or challenges the conclusion.

56
00:03:35,340 --> 00:03:39,385
Independent validation follows the
completed pass before a proposed

57
00:03:39,400 --> 00:03:41,240
correction becomes accepted work.

58
00:03:41,740 --> 00:03:44,040
The same discipline applies to
simplification.

59
00:03:44,480 --> 00:03:48,465
A check may look cumbersome while
protecting privacy, preserving recovery

60
00:03:48,480 --> 00:03:52,120
history, or preventing an uncertain action
from being repeated.

61
00:03:52,980 --> 00:03:56,920
Understanding that responsibility comes
before deciding which parts to remove.

62
00:03:57,520 --> 00:04:01,100
This is where the audit connects with the
way we plan and build Brava.

63
00:04:01,660 --> 00:04:06,485
Conversational AI can help explore an idea
and produce a prototype quickly, a

64
00:04:06,500 --> 00:04:08,600
practice often called vibe coding.

65
00:04:09,000 --> 00:04:12,300
It's useful for discovering possibilities
and trying them out.

66
00:04:12,720 --> 00:04:16,800
AI assisted engineering, on the other
hand, brings explicit requirements,

67
00:04:17,180 --> 00:04:21,445
architectural decisions, reproducible
checks, and evidence required for

68
00:04:21,460 --> 00:04:23,240
acceptance to the generated work.

69
00:04:23,620 --> 00:04:27,680
The distinction is in how that work is
directed, examined, and accepted.

70
00:04:28,120 --> 00:04:32,620
The tools can overlap. The engineering
responsibilities still need owners.

71
00:04:33,140 --> 00:04:36,000
At Mevanu, that begins before
implementation.

72
00:04:36,860 --> 00:04:41,365
Architectural design, anticipated
challenges, and dependency planning feed

73
00:04:41,380 --> 00:04:46,025
detailed roadmaps and engineering
blueprints, structured for both human and

74
00:04:46,040 --> 00:04:50,725
machine reading. They connect the intended
behavior to responsibilities, build

75
00:04:50,740 --> 00:04:52,540
order, and acceptance checks.

76
00:04:53,040 --> 00:04:55,700
The founder sets the purpose and approves
scope.

77
00:04:56,200 --> 00:05:00,225
Our executive partner coordinates the work
and its evidence, while the systems

78
00:05:00,240 --> 00:05:04,825
architect examines ownership, contracts,
and the wider consequences of a

79
00:05:04,840 --> 00:05:09,365
design. An engineer implements an agreed
change, and independent assurance

80
00:05:09,380 --> 00:05:11,640
challenges the evidence for accepting it.

81
00:05:12,040 --> 00:05:15,845
Frontier Lab and scholarly research feed
this structure through concrete

82
00:05:15,860 --> 00:05:20,540
proposals. What a result could mean for
Brava, which assumptions carry over,

83
00:05:20,760 --> 00:05:23,060
and how the proposed behavior could be
tested.

84
00:05:23,580 --> 00:05:28,105
Decisions, corrections, and unresolved
questions remain available to the next

85
00:05:28,120 --> 00:05:31,880
task, so planning can follow the actual
state of the build.

86
00:05:32,280 --> 00:05:36,805
At Mevanu, we constantly strive to balance
timely development with strict

87
00:05:36,820 --> 00:05:38,540
quality assurance and governance.

88
00:05:39,540 --> 00:05:43,125
Spending tokens repeatedly patching a
stack that cannot hold up in installed

89
00:05:43,140 --> 00:05:47,300
app testing consumes effort without
resolving the underlying problem.

90
00:05:47,800 --> 00:05:51,865
The useful move is to step back, identify
the design constraint, and

91
00:05:51,880 --> 00:05:53,300
reconsider the approach.

92
00:05:53,900 --> 00:05:55,680
Build order matters just as much.

93
00:05:56,100 --> 00:06:00,645
A planned feature may depend on a shared
contract, a persistence mechanism, or

94
00:06:00,660 --> 00:06:03,200
a recovery path that should be established
earlier.

95
00:06:03,800 --> 00:06:07,325
Missing that engineering window can leave
us retrofitting foundations through

96
00:06:07,340 --> 00:06:11,900
several completed features, increasing
both cost and regression risk.

97
00:06:12,420 --> 00:06:14,900
Our repair protocol makes that balance
practical.

98
00:06:15,460 --> 00:06:19,485
Make a supported correction, check the
affected behavior promptly, and

99
00:06:19,500 --> 00:06:22,200
preserve working fixes in recoverable
checkpoints.

100
00:06:22,800 --> 00:06:27,425
After three unsuccessful repairs of the
same problem, stop patching and

101
00:06:27,440 --> 00:06:31,785
reconsider the ownership, contract, or
design before trying another

102
00:06:31,800 --> 00:06:36,040
implementation. That approach also shapes
our use of automated checks.

103
00:06:36,900 --> 00:06:40,745
Earlier iterations had a configured lint
and type check pipeline, including

104
00:06:40,760 --> 00:06:45,900
ESLint with no warnings accepted and
OpenAPI checks of the API definitions.

105
00:06:46,760 --> 00:06:48,540
Lint can catch certain code problems.

106
00:06:48,940 --> 00:06:53,005
It cannot establish that an export
preserves someone's text or that a late

107
00:06:53,020 --> 00:06:55,220
response leaves their newer work intact.

108
00:06:55,920 --> 00:07:00,445
Type checks, unit tests, builds, and
end-to-end tests answer different

109
00:07:00,460 --> 00:07:04,920
questions. The current native snapshot
declares JavaScript syntax checks,

110
00:07:05,420 --> 00:07:08,400
JavaScript and Swift test suites, and
Xcode checks.

111
00:07:08,940 --> 00:07:12,705
This audit examines whether those checks
match the code and whether their

112
00:07:12,720 --> 00:07:15,420
assertions establish the behavior being
claimed.

113
00:07:16,100 --> 00:07:20,045
Codex has supported earlier debugging,
localized repairs, and focused

114
00:07:20,060 --> 00:07:24,625
verification. We've also used Daybreak
Blue often in our previous workflows.

115
00:07:24,640 --> 00:07:29,445
It's OpenAI's offering for authorized
defensive security work, supporting

116
00:07:29,460 --> 00:07:33,765
activities such as vulnerability
investigation, secure code review, and

117
00:07:33,780 --> 00:07:35,180
checking proposed fixes.

118
00:07:35,460 --> 00:07:39,560
For this audit, a separate Daybreak Blue
hardening review remains planned.

119
00:07:40,200 --> 00:07:44,045
Prior experience with it helps us choose
an appropriate review, but it doesn't

120
00:07:44,060 --> 00:07:46,920
replace examining this particular source
snapshot.

121
00:07:47,440 --> 00:07:50,160
Each assessment needs its own scope and
evidence.

122
00:07:50,680 --> 00:07:54,105
The findings so far point toward focused
corrections and bounded

123
00:07:54,120 --> 00:07:58,325
simplifications. The remaining coverage
will test that picture before the

124
00:07:58,340 --> 00:08:00,700
report is frozen for independent
assurance.

125
00:08:01,220 --> 00:08:05,505
That review will challenge coverage,
reasoning, counterevidence, and repair

126
00:08:05,520 --> 00:08:10,040
priorities. Supported repairs can then
proceed within their approved scope.

127
00:08:10,540 --> 00:08:14,800
The repaired successor will be frozen for
one blind GitHub Copilot review,

128
00:08:14,900 --> 00:08:19,325
with earlier findings and repair
explanations withheld until its own report

129
00:08:19,340 --> 00:08:24,145
is recorded. Any new supported concerns
will be checked before final candidate

130
00:08:24,160 --> 00:08:27,960
assurance examines the changes and their
acceptance evidence.

131
00:08:28,620 --> 00:08:33,240
Today's stream has ended, while the audit
continues and Gate 7 remains open.

132
00:08:33,700 --> 00:08:37,620
Our next update will follow the completed
review, the corrections it supports,

133
00:08:37,800 --> 00:08:39,420
and the results of those checks.

134
00:08:40,000 --> 00:08:43,460
That sequence gives us something concrete
to report at each stage.

135
00:08:44,080 --> 00:08:48,345
Thank you for following the work here at
Ordering Lunch for One at Mevanu.ai.

136
00:08:48,360 --> 00:08:50,560
Have an idea? A solution?

137
00:08:51,080 --> 00:08:55,780
See something we're missing? Drop a
prompt, comment, suggestion, or question.

138
00:08:56,380 --> 00:08:58,240
Mevanu. A little further.

139
00:08:58,800 --> 00:08:59,520
Every time.